Connected Vehicle Settings and Cloud System Management

ABSTRACT

A cloud system that includes one or more servers for communicating with vehicles and processing information received from vehicles and processing information sent to vehicles is disclosed. One method includes receiving data from a computing device associated with a vehicle. The data is for a user account, and the data is received over one or more sessions. The user account has a user profile with a plurality of settings and metadata captured from use of the vehicle. Processing, by a learning engine, the metadata captured from use of the vehicle during the one or more sessions of use of the vehicle to identify learned patterns sensed from the vehicle. Sending a recommendation to the user account associated with the vehicle. The recommendation is based in part on the learned patterns from the vehicle. The recommendation is configured to identify a setting or action for the vehicle. The setting or action is configured to be accepted via a user interface associated with the user account to apply said setting on the vehicle or confirm said action for the vehicle.

CLAIM OF PRIORITY

This application is a continuation of U.S. patent application Ser. No.15/243,948, filed on Aug. 22, 2016, entitled “Connected Vehicle Settingsand Cloud System Management,” which is a continuation of U.S. patentapplication Ser. No. 15/071,120, filed on Mar. 15, 2016 (now U.S. Pat.No. 9,426,225 issued on Aug. 23, 2016) entitled “Connected VehicleSettings and Cloud System Management,” which is a continuation of U.S.patent application Ser. No. 14/952,911, filed on Nov. 25, 2015 (now U.S.Pat. No. 9,288,270 issued on Mar. 15, 2016), entitled “Systems forLearning User Preferences and Generating Recommendations to makeSettings at Connected Vehicles and Interfacing with Cloud Systems,”which claims priority as a continuation of U.S. patent application Ser.No. 14/790,409, filed on Jul. 2, 2015 (now U.S. Pat. No. 9,215,274issued on Dec. 15, 2015), entitled “Methods and Systems for GeneratingRecommendations to make Settings at Vehicles via Cloud Systems,” whichclaims priority as a continuation of U.S. patent application Ser. No.13/906,335, filed on May 30, 2013 (now U.S. Pat. No. 9,104,537 issued onAug. 11, 2015), and entitled “Methods and Systems for Generating SettingRecommendation to User Accounts for Registered Vehicles via CloudSystems and Remotely Applying Settings,” which claims priority as acontinuation-in-part of U.S. patent application Ser. No. 13/842,158,filed Mar. 15, 2013 (now U.S. Pat. No. 9,229,905 issued on Jan. 5,2016), and entitled “Methods and Systems for Defining User Profiles andManaging User Profiles via Cloud Systems and Applying Learned Settingsto User Profiles,” and which claims priority to U.S. Provisional PatentApplication No. 61/745,729, filed on Dec. 24, 2012, and entitled“Methods and Systems For Electric Vehicle (EV) Charging, ChargingSystems, Internet Applications and User Notifications”, which is hereinincorporated by reference.

U.S. patent application Ser. No. 15/071,120, filed on Mar. 15, 2016 isalso a continuation-in-part of U.S. application Ser. No. 13/784,823,filed on Mar. 5, 2013 (now U.S. Pat. No. 9,285,944 issued on Mar. 15,2016) and entitled “Methods and Systems for Defining Custom Vehicle UserInterface Configurations and Cloud Services for Managing Applicationsfor the User Interface and Learned Setting Functions,” which is hereinincorporated by reference.

U.S. patent application Ser. No. 14/790,409, filed on Jul. 2, 2015 is acontinuation-in-part of U.S. application Ser. No. 14/176,138, filed onFeb. 9, 2014 (now U.S. Pat. No. 9,697,503 issued on Jul. 4, 2017) whichis entitled “Methods and Systems for Providing Recommendations toVehicle users to Handle Alerts Associated with the Vehicle and A BiddingMarket Place for Handling Alerts/Service of the Vehicle,” which isincorporated by reference herein.

U.S. patent application Ser. No. 14/790,409, filed on Jul. 2, 2015 is acontinuation-in-part of U.S. application Ser. No. 13/452,882, filed Apr.22, 2012 (now U.S. Pat. No. 9,123,035 issued on Sep. 1, 2015) andentitled “Electric Vehicle (EV) Range Extending Charge Systems,Distributed Networks Of Charge Kiosks, And Charge Locating Mobile Apps”,which claims priority to U.S. Provisional Application No. 61/478,436,filed on Apr. 22, 2011, all of which are incorporated herein byreference.

FIELD OF THE EMBODIMENTS

The present invention relates to systems and methods for managing userprofiles for vehicles and exchange of information with cloud-basedprocessing systems.

BACKGROUND

Vehicles, such as motorized vehicles and electric vehicles have beenaround for some time. Vehicles provide a means that enable humans todrive from place to place. In today's world, vehicles have become anindispensable mode of transportation, and provide the freedom to travelat any time of day and for various distances. Vehicles can be publicallyoperated or can be privately owned. Humans most commonly operatevehicles, no matter the type, whether electric or combustion enginebased. In recent years, technology has been advancing to allow forbetter wireless interfacing and networking with vehicles.

It is in this context that embodiments of the invention arise.

SUMMARY

The methods, systems and apparatus include electronics of vehicles thatdrive display devices in vehicles and communicate wirelessly withInternet services. Methods and systems provide access to cloud servicesover the Internet for managing a user profile of a vehicle on a cloudprocessing system connected to the Internet. One example method includesreceiving requests to access the user profile to define settings for oneor more vehicles. The method includes receiving input for user settingsat the vehicle using the cloud processing system. The method includesprocessing the input over time to learn behavior associated with theinput to the use settings. The method includes transmitting settings tothe vehicle to be automatically implemented based on the learnedbehavior. In one example, the profile is associated with a plurality ofvehicle types and the method includes detecting a violation of a settingor an incompatible setting in the profile that is user defined via theuser account. The method can then automatically send a notification to apredefined administrator of the profile. The method being executed by aprocessor.

In one embodiment, a method includes establishing a communication linkbetween a computing device associated with a vehicle and a server. Thecommunication link is over a wireless network and the communication linkis established in association with a user account. The communicationlink is established for one or more sessions. The method furtherincludes receiving, at the server, a plurality of actions associatedwith inputs to the vehicle. The plurality of actions are received duringthe one or more sessions, and generating, by the server, arecommendation to program a setting at the vehicle. One or more of theplurality of actions at the vehicle during the one or more sessions areprocessed to determine a confidence score associated with generating therecommendation to program the setting. Generation of the recommendationoccurs upon reaching or exceeding a predefined threshold. The serverthen sends to the user account the recommendation to enable programmingof the setting for the vehicle.

In one embodiment, a method for processing information associated with avehicle is disclosed. The method includes receiving a plurality ofactions set at the vehicle over a period of time. The actions can bereceived from a server or services of a provider. The method includesupdating a history profile for a user account of the vehicle for theplurality of actions. The history profile includes metadata for each ofthe plurality of actions. The method generates confidence scores foreach of the plurality of actions in the history profile and generatingone or more action recommendations that can be accepted forimplementation by the vehicle. For actions having confidence scores thatexceed a threshold, the method sends the one or more actionrecommendations to the user account associated with the vehicle. Theaction recommendations include an accept or decline option that can beset via the user account to cause data to be received indicative of theoption. For action recommendations that are accepted, the methodincludes setting a time to send a programming instruction to the vehicleand sending the programming instruction to the vehicle to cause thevehicle to programmatically perform a programmed action to implement atleast one of the action recommendations. In one embodiment, the actionrecommendations are vehicle settings.

In some embodiment, the metadata of each action includes a record of atime and date of each occurrence and for actions that show a repeatingpattern of occurrences will have an increased confidence score. Thethreshold is predefined to require a set number of occurrences of theactions to occur so that the repeating pattern is identifiable.

In some embodiment, confidence scores are increased for actions thatreoccur multiple times at about a similar time and date, and theconfidence scores are decreased for actions that do not reoccur multipleat about the similar time and date or occur at dissimilar times anddates.

In some embodiments, increases in actions that reoccur multiple times atabout a similar time and date have a repeating pattern that isindicative of a likelihood that the action recommendation will beaccepted.

In some embodiments, the actions set at the vehicle are selected fromone or more of setting a temperature of the vehicle, setting a windowdefrost mode in the vehicle, heating a seat or seats of the vehicle,setting an emergency signal of the vehicle, setting an emergency signalfor help, setting a restriction or enabling a feature for the vehicle,disabling the vehicle, selecting an audio setting, making a reservationfor service, reporting an error in the vehicle, setting a position ofmirrors of the vehicle, setting to open or crack windows upon reaching atemperature, setting notifications for recharging a battery if thevehicle is an electric vehicle, setting reminders to charge uponreaching a predefined battery state if an electric vehicle, settingparameters to identify nearby charge stations if the vehicle is anelectric vehicle, setting advertisement settings allowed to be displayedvia a screen of the electric vehicle, setting maps data, settingcommunications data, setting navigation data, setting display settingsdata, setting customization of display applications on the screen of thevehicle, setting suspension parameters for the vehicle, setting autolock/unlock controls of the vehicle, activating an alarm, settinginstructions to receive video feedback from the vehicle upon detectionof alarm conditions, setting to call for help when an accident isdetected, setting time of day on vehicle clocks based on local time;setting navigation parameters in the vehicle, setting preferred radiostations, setting sensitivity of collision detection sensors, settingsensor programming, or combinations of two or more thereof.

In some embodiments, the method may include receiving sensor data fromthe vehicle. The sensor data is associated to particular ones of theplurality of actions, the sensor data being saved to the metadata of therespective actions in the history profile.

In some embodiments, the sensor data includes one or more of actualsensed temperature, geo-location, speed, vehicle condition, occupantidentification, number of occupants sensed, biometric detection of anoccupant in the vehicle, proximity of surrounding vehicles or obstacles,voice data, video data, touch data, gesture data, surrounding vehicleshared sensor data, or at combination of two or more thereof.

In some embodiments, the confidence score for an action in the historyprofile is increased for actions having repeat occurrences while havingsimilar sensor data present in the metadata of the actions, or theconfidence score for an action in the history profile is increased foractions having repeat occurrences and having same sensor data present inthe metadata of the actions

In some embodiments, a method includes, for particular sensorsassociated with particular actions, making the action recommendationinclude, sending data to populate a user interface of a computing devicewith a control to accept or decline the option, the data sent is via anetwork connected to the Internet. In one example, the computing deviceis one of a vehicle computing device, or a mobile computer device, or atablet computing device, or a smart phone computing device, or aninternet terminal computing device, or a non-portable computing device.

In some embodiments, the data is sent to the user account, the useraccount being accessible over the Internet.

In some embodiments, when the sensor is a temperature sensor and theaction is inputting a heating or cooling setting at the vehicle, theaction recommendation includes, and sending data to populate a userinterface of a computing device with a control to accept or decline theoption, the data sent is via a network connected to the Internet. In oneexample, the computing device is one of a vehicle computing device, or amobile computer device, or a tablet computing device, or a smart phonecomputing device, or an internet terminal computing device, or anon-portable computing device. In one example, the data is sent to theuser account, the user account being accessible over the Internet.

In some embodiments, the heating or cooling setting includes one or moreof activating a window defrost setting, or activating a heating setting,or activating an air conditioning setting, wherein the actionrecommendation for the heating or cooling setting at least in part usesweather forecast data obtained from the Internet for a predictedgeo-location of the vehicle.

In some embodiments, a method can further include receiving temperaturedata from a sensor of the vehicle; determining that the receivedtemperature is inconsistent with the weather forecast; andprogrammatically declining the action recommendation if the actionrecommendation was initially accepted, such that the programminginstruction is not sent to the vehicle or is updated so as to cancel theprogramming instruction.

In some embodiments, confidence scores for actions that exceed athreshold is indicative that such action will more likely than not occuragain at a future time.

In some embodiments, a method can further include: accessing third-partyhistory profiles of other user accounts; examining the actions andmetadata of the third-party history profiles to identify similar actionsand patterns to those of the history profile; adjusting one or more ofthe action recommendations based on the examining, and the adjusting maybe weighted to provide more significance to metadata in the historyprofile than that in the third-party history profiles.

In some embodiments, the action recommendations change over time basedon changes in patterns detected in the history profile.

In some embodiments, changes in action recommendations include removalof previously accepted action recommendations when either override ofactivating the action is detected to occur a number of times or changesin patterns of use of the actions at the vehicle suggested removal ofthe previously accepted action recommendation.

In some embodiments, the third-party history profiles and the historyprofile are defined as one or more databases on storage accessible by aserver that is accessible over the Internet. In one example, the vehicleuses communication logic for communicating with the server over theInternet. In one example, the server further includes logic for sendingthe action recommendations to devices of a user having the user accountfor the vehicle.

In some embodiments, a server executes cloud processing logic to performoperations method operations. In one example, client devices andvehicles devices can communicate with the server and cloud processinglogic to exchange data

In another embodiment, a method for recommending settings to be appliedat a vehicle registered to a user account are provided. The recommendingis processed by a server that receives data from the vehicle over anetwork and sends action recommendations to one or more predefined userdevices associated with the user account. The method includes (a)receiving information at the server that a plurality of actions havebeen applied at the vehicle over a period of time; (b) updating ahistory profile for a user account of the vehicle for the plurality ofactions, the history profile includes metadata for each of the pluralityof actions; (c) generating confidence scores for each of the pluralityof actions in the history profile, the confidence scores are saved tothe metadata of the history profile; (d) generating one or more actionrecommendations, that can be accepted for implementation by the vehicle,for actions having confidence scores that exceed a threshold; (e)sending the one or more action recommendations to the user accountassociated with the vehicle, the action recommendations including anaccept or decline option that can be set via the user account to causedata to be received indicative of the option, for action recommendationsthat are accepted, (i) setting a time to send a programming instructionto the vehicle; and (ii) sending the programming instruction via thenetwork to the vehicle to cause the vehicle to programmatically performa programmed action to implement at least one of the actionrecommendations, the action recommendations being vehicle settings. Themetadata of each action includes a record of a time and date of eachoccurrence and for actions that show a repeating pattern of occurrenceswill have an increased confidence score, wherein the threshold ispredefined to require a set number of occurrences of the actions tooccur so that the repeating pattern is identifiable, and wherein themethod being executed by a processor.

In still another embodiment, a method for recommending settings to beapplied at a vehicle registered to a user account is provided. Therecommending is processed by a server that receives data from thevehicle over a network and sends action recommendations to one or morepredefined user devices associated with the user account. The methodincludes (a) receiving information at the server that a plurality ofactions have been applied at the vehicle over a period of time; (b)updating a history profile for a user account of the vehicle for theplurality of actions, the history profile includes metadata for each ofthe plurality of actions; (c) generating confidence scores for each ofthe plurality of actions in the history profile, the confidence scoresare saved to the metadata of the history profile; (d) generating one ormore action recommendations, that can be accepted for implementation bythe vehicle, for actions having confidence scores that exceed athreshold; (e) sending the one or more action recommendations to theuser account associated with the vehicle, the action recommendationsincluding an accept or decline option that can be set via the useraccount to cause data to be received indicative of the option, foraction recommendations that are accepted, (i) setting a time to send aprogramming instruction to the vehicle; and (ii) sending the programminginstruction via the network to the vehicle to cause the vehicle toprogrammatically perform a programmed action to implement at least oneof the action recommendations, the action recommendations being vehiclesettings, (f) accessing third-party history profiles of other useraccounts; (g) examining the actions and metadata of the third-partyhistory profiles to identify similar actions and patterns to those ofthe history profile; and (h) adjusting one or more of the actionrecommendations in (d) based on the examining of (g), the adjustingbeing weighted to provide more significance to metadata in the historyprofile than that in the third-party history profiles.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 shows example profiles settings for a vehicle, and association toroles, in accordance with one embodiment.

FIG. 2 shows additional role settings for different users, in accordancewith one embodiment.

FIGS. 3-5 show additional vehicle profile settings, in accordance withone embodiment.

FIGS. 6-9B show example pairing of a vehicle to a user profile, andexamples of a shared vehicle transfers of profiles for limited use ofthe profiles on the shared vehicles, in accordance with one embodiment.

FIG. 10 illustrates validation method for enabling a profile on avehicle and biometric validation, in accordance with one embodiment.

FIG. 11 illustrates various settings for a profile and adjustments thatcan be made over the Internet via a device, e.g., using a portabledevice or the vehicle electronics and displays, and remote controls andsettings in accordance with one embodiment.

FIG. 12 describes a system in which a user interacts with a model viewcontroller software environment useful for processing APPS using APIs onvehicles with vehicle operating systems capable of processing computercode, in accordance with one embodiment.

FIG. 13A describes how vehicle on board computer with input outputsystem useful for accepting input, processing input and displayingresults in conjunction with stored computer readable programs orfunctions in the forms of APPs may be structured, in accordance with oneembodiment.

FIG. 13B describes one example of how stored data and functiondeclarations may be compiled to provide intermediary access to avehicle's computer controlling vehicle systems, in accordance with oneembodiment.

FIG. 13C describes a set of computer readable and executable code thatcan be compiled together by a third party APP developer in the form ofan APP, in accordance with one embodiment.

FIG. 14 describes the stepped flow of events as a user interacts with anAPP, in this case, an HVAC APP, in accordance with one embodiment.

FIG. 15 Describes further ways an APP may take, process and produceresults, in accordance with one embodiment.

FIG. 16A describes an ecosystem where an APP in conjunction with avehicle API may work together to make assumptions, make decisions andtake actions, in accordance with one embodiment.

FIG. 16B describes how one of many types of inputs into an assumptionand reasoning logic module can be compiled over time, in accordance withone embodiment.

FIG. 16C describes one example of what an assumption and reasoning logicmodule may produce using the data points collected on an ongoing basisin FIG. 16B, in accordance with one embodiment.

FIG. 16D describes an example list of decision the decision and actionengine may take based on information provided by the assumption andreasoning logic module and sets of assumptions created, in accordancewith one embodiment.

FIG. 17 provides an example of a recommendation process, forrecommending actions to set at vehicles based on detected user patternsor use, and sending recommendations and programming settings, inaccordance with one embodiment.

DETAILED EMBODIMENTS

Embodiments of the present invention define methods, systems andapparatus for use in vehicles. The methods, systems and apparatusinclude electronics of vehicles that drive display devices in vehiclesand communicate wirelessly with Internet services.

The Internet services provide access to cloud services. The cloudservices provide access to user accounts and access to settings,configurations, applications and other customization defined by theuser. Customization can include user interface customization of avehicle display or displays. The customization can include the abilityto select specific applications (APPS) to be activated by the vehicleand interfaced via the display or displays, voice input, touch input,etc. The customization is also provided with a learning engine thatlearns use behavior by the user or patterns of behavior of multipleusers, and automatically implements settings or programming to aspectsof the user interface, or provides recommendations or notifications withrecommendations. The programming can include automatic programming atcertain times, days, months, years, etc., and can be updated or moldedover time as the user continues to use the vehicle UI.

In one embodiment, a user can access cloud services for a vehiclemanufacturer and identify the particular vehicle from selected choices.The user can then identify a customization profile for the vehicle bydefining the look and feel of a UI display, arrangement of vehiclecontrols on displays, add and associate third party APPS to the vehicledisplay, and save the configuration.

The configuration, in one embodiment, is saved to the profile of theuser. In one embodiment, the profile is saved on a database of aspecific vehicle manufacturer that offers the customization option. Instill other embodiments, once a configuration is saved to the profileaccount of a user, that configuration can be shared to other vehicles ofthe user. In still other embodiments, when a user buys a new car, thecustom configuration can be transferred either entirely or partially tothe new vehicle. In some embodiments, if the vehicle has more or lesssystem functions, the customization can be adjusted automatically or theuser can be provided with options to update the customization to add ordelete features. In one embodiment, the customization will befacilitated via a website. In one embodiment, the website may be of thevehicle manufacturer. In one embodiment, the website of the vehiclemanufacturer can allow the user to add APPS that are created by thirdparties. The third parties can create APPS that communicate with APIs ofthe system components of specific vehicles of the manufacturer. OnceAPPS are selected, the user can add them to the custom user interface(UI) display.

The user can also be allowed to arrange the APPS or icons of APPS in aspecific custom arrangement that is saved to the user's profile. In oneembodiment, the user's profile can also be run on various vehicles,other than those owned by the user. For instance, if the user is rentinga vehicle and the vehicle has access to cloud services, the user canenter his user name and password (or other identifiers), which log theuser into the cloud services and saved profiles. The saved profiles willthen enable logic to build a custom UI for the user based on the vehiclebeing driven. In one embodiment, the system components and APIs of thesystem components of the rented vehicle can be paired or linked to theuser's saved APP selections.

The user's saved UI configuration may also be transferred to the displayof the rented (or other vehicle) vehicle. A best-fit configuration canalso be generated using the user's profile selections, so that theconfiguration provided for the other vehicle will closely resemble orappear as it does for the configured vehicle. In other embodiments, theuser's use metrics can be monitored. The use metrics can include use ofAPPS, use be of system components of the vehicle, use of the vehicle,environment conditions, and historical actions taken by the user via theinput/output controls of the vehicle (e.g., buttons, levers, keys, fobs,display selections, display interface actions, communication actions,etc.).

These historical actions can then be used to define learned actions. Thelearned actions can be analyzed to change configuration settings in theuser's saved profile. For instance, if the user uses a particular APPevery day at a particular time, that APP icon can be surfaced to thedisplay or preset to start. The APP can then provide information to theuser at about the same time the user normally needs the information.Other historical use patterns can be monitored and such data can besaved to the user's profile.

The data can then be used by algorithms that build assumptions based onhistorical inputs by a user as well as environmental inputs, locationinputs, vehicle diagnostic inputs, internet connected marketing deals,the user's calendar, traffic conditions as well as news. The assumptionsthe algorithm builds are then processed into decisions and actions by anadditional algorithmic process to activate local or remote audio andvisual alerts, change vehicle systems, display information on avehicle's displays and request a decision from a user locally orremotely to complete an action.

A number of embodiments are described below, with reference to specificimplementations that refer to vehicles, but such implementations shouldbe broadly construed to include any type of vehicle, structure orobject. Without limitation, vehicles can include any type of movingobject that can be steered, and can include vehicles that are for humanoccupancy or not. Vehicles can include those that are privately owned,owned by corporations, commercially operated vehicles, such as buses,automobiles, trucks, cars, buses, trains, trolleys, etc. Examplevehicles can include those that are combustion engine based, electricengine (EV) based, hybrids, or other types of energy source vehicles.

A cloud processing system, as described herein, will include systemsthat are operated and connected to the Internet or to each other usinglocal networking communication protocols. A cloud processing system canbe defined as an interconnected and distributed physical or virtualsoftware defined network that utilizes virtual or physical processingand storage machines that enable various applications and operatingsystems to facilitate the communication with and between various clientdevices (vehicles, user devices, structures, objects etc.).

The communication with and between the various client devices willenable the cloud processing system to deliver additional processinginformation, data, and real-time metrics concerning data obtained fromother processing systems as well as client feedback data. Thedistributed nature of the cloud processing system will enable users ofvarious vehicles, structures and objects to access the Internet, and bepresented with more flexible processing power that will provide therequested services in a more effective manner.

The processing systems can be defined from various data centers thatinclude multiple computing systems that provide the processing power toexecute one or more computer readable programs. The processing of thecomputer readable programs can produce operations that can respond torequests made by other processing systems that may be local to avehicle's electronic system. For example, a vehicle can includeelectronics that utilize memory and a processor to execute programinstructions to provide services.

In other embodiments, the electronics of a vehicle can synchronize witha user's portable electronics. The user's electronics can include, forexample mobile devices that include smartphones, tablet computers,laptop computers, general-purpose computers, special purpose computers,etc. The various computing devices of the vehicle, and or the computingdevices of the user (smart devices) can be connected to the Internet orto each other. Provided that a user has access or account access to thecloud service, the cloud processing services on the Internet can provideadditional processing information to the electronics of the vehicle.

The wireless communication can include cellular tower communication thatcouples and communicates through various networks to the Internet, toprovide access to cloud processing 120. Other methods can includeproviding Wi-Fi communication to local Wi-Fi transmitters and receivers,which communicate with cloud processing 120. Other types ofcommunication can include radio frequency communication, such as802.11.ac, 802.11ad and subsequent wireless networking protocols,Bluetooth communication or combinations of Wi-Fi and Bluetooth. Itshould be understood that vehicle electronics can communicate with cloudprocessing 120 via any number of communication methods, so long asexchanges of data can be made with cloud processing 120 from time totime.

The communication can be made by vehicle electronics while the vehicleis on or when the vehicle is off, so long as communication andprocessing circuitry of vehicle electronics has a power source. Thepower source can include battery power that powers vehicle electronicsto communicate with cloud processing 120 when vehicle is turned off.When vehicle is turned on, the battery that drives vehicle electronicscan be recharged.

Still further, certain applications can increase in size when being usedor decrease in size to enable selection at a later time. For example,selecting the temperature system component may expand the systemcomponent to a larger space, thus temporarily removing other displayedcomponents. The user can also select other buttons to access othersystem controls, other apps, or modify or add applications or systemcontrols. When modifications are made, the modifications are saved to auser database and profile of the user, as managed by cloud services.

Cloud services will therefore allow any future modifications to be madeto the custom configuration at any time and from any computer connectedto the Internet. Still further, the custom configuration can betransferred to a second vehicle. If the custom configuration istransferred to a second vehicle, the system can select the systemcomponents for the second vehicle and attempted do a best match ofapplications available for the second vehicle that resemble or match theones used in a first vehicle. Specific settings, arrangements and otherfeatures may also be transferred to a second vehicle, by simplytransferring the custom configuration to a second vehicle.

In one embodiment, the functions of the specific applicationsillustrated in the display will be monitored and restricted depending onsafety considerations while driving. For example, if the interfacingfunctionality requires more interactivity with the display, or requiresa reading of text or inputting text, those functions will be disabledduring operation of the vehicle. Once the vehicle comes to a stop, or isplaced in Park, certain of these functions will be activated. In otherembodiments, other safety considerations will allow for applications toshift from outputting text to outputting audio or voice. The input canalso be changed from touchscreen, button touches, selections, and/orvoice input. In still other embodiments, safety considerations can allowcertain user interface components to move about the display to provideeasier reading while driving or automatic conversion of text to audio.

For example, content being displayed in the center panel display of thevehicle, can be automatically shown in the dashboard display region ofthe vehicle, such as in front of the steering wheel. In still otherembodiments, some content or display data can be moved from the centerconsole or the display in front of the steering wheel to the windshieldof the vehicle in a heads-up display area. Accordingly, algorithmsexecuted by the applications and applications of the manufacturer, cancooperate to provide functionality to the application features andinterfaces, while maintaining safety parameters defined by rules. Thesafety parameters will therefore allow content of the user interface tobe shifted around to various displays of the vehicle, or translated tovoice or audio at certain points in time.

These settings and customizations can be made through the web/cloudservices and tools provided by the website of, for example themanufacturer of the vehicle. In one embodiment, the cloud servicesprovided by the manufacturer can be provided by a partner of themanufacturer. The partners of the manufacturer can include softwarecompanies that develop, host, or manage certain functionality providedby the vehicle manufacturer. In other embodiments, the partner softwarecompanies can integrate tools or components with tools and components ofthe vehicle manufacturer. This provides for integration with one or morecloud services, software services, Internet services, and servicesprovided by systems of vehicles or systems of the vehicle manufacture.In either case, whether the software and logic is designed andconstructed by one or more entities, the cloud services provided by thevehicle manufacturer or the website that provides the tools forcustomization will appear as a unified simple to use interface for theuser. As mentioned above, the cloud services can provide databases forsaving the user profile and data associated with the user account.

The user profile can include settings made by the user, customizationsmade by the user, identification of applications purchased or added tothe vehicle customizations, etc. Still further, the user profile datacan be part or be associated with the user account. In this manner, theuser that customized a user interface can access the Internet at anytime, whether through the vehicle or through any other computing devicehaving access to the Internet and make changes, modifications, or accesscontrol features of the vehicle remotely. In one embodiment, the profileof the user can be accessed from any vehicle, such as rented vehicles orshared vehicles. Settings and profile data can then be shared for aperiod of time on any vehicle and use data on that vehicle can bestored.

When the user is not using the vehicle, the custom configuration can beturned off or locked out for another session. Once the user wants tostart a new session, the user can log back in and the customconfiguration returns. In other embodiments, the custom configurationwill automatically turn off when the user is not driving the vehicle orhas not logged into the vehicle. In other embodiments, the customconfiguration can be automatically turned on when the user is detected.The user can be detected using biometrics, login credentials, imagedetection of the face, fingerprint detection, retina scans, etc. In someembodiments, biometrics can include data used to identify the user, suchas face recognition, fingerprint reading, retina scans, voice detection,or combinations thereof. Still further, the custom configuration can betransferred to other vehicles.

If the user wishes to use his or her custom configuration in anothervehicle, the user can login to the custom configuration or user accountfrom another vehicle. If the other vehicle does not have all the systemcomponents needed to define the custom configuration, the customconfiguration can be supplemented with other similar componentsautomatically. In other embodiments, the custom configuration can betransferred from one vehicle to another, or when the user buys a newvehicle. In another embodiment, the custom configuration can be adjustedbased on the driver. The custom configuration can also be presetremotely from the Internet, using the cloud services. The customconfiguration can also be configured to provide limited use of certainsystems or the vehicle, such as when a guest is driving the vehicle. Inother embodiments, restrictions can be placed on the vehicle speed,location of driving, and automatic notifications for the user or themaster user of the vehicle. The master user of the vehicle can have amaster account with administrator credentials.

In still another embodiment, the vehicle can be loaned to a child ofdriving age (under 21/18 years of age), and the child can be providedwith restricted use of the vehicle. When the child exceeds or does notfollow the restrictions of the vehicle, automatic notifications can beprovided to the user that is the administrator of the vehicle. Thenotifications can be by cell phone, smartphone, tablet computer, mobiledevice, text messages, phone calls, commendations of phone calls andtext, audio messages, audible sounds, vibrations, and commendationsthereof. History use of the vehicle can also be maintained in cloudservices. The history use can provide the user with information as towhere the vehicle has been, the speed or events, violations thatoccurred when use of the vehicle etc. The configuration can also providemessages to the driver warning the driver of when the vehicle hasexceeded a restriction, or is approaching a restriction in use, drivingarea, speed, etc.

The screen displays can have various configurations, placements, sizes,number of pages, tabs, etc., and the user can provide controls for someor all of the interfaces and controls in certain locations. Theselection can be enabled for third-party applications. The third-partyapplications can be selected from the vehicle site, or by providinglinks to third-party sites. The third-party applications can bepre-identified by the site and displayed to the user if they arecompatible with the particular vehicle selected. In another embodiment,the third-party applications can all be shown to the user whether or notthey are compatible with the vehicle. Upon binding/pairing or attemptingto find application for the vehicle, compliance as to whether theapplications operate or comply with the particular vehicle can be made.

In one embodiment, certain third-party applications can be reviewed bythe vehicle site administrators before they are made available to usersfor selection. In other embodiments, the third-party applications can beapproved or disapproved. In still other embodiments, the third-partyapplications can be augmented with restrictions made by the vehiclemanufacturer, or dictated by law. The restrictions can be applied, basedon the anticipated interfacing with the vehicle interfaces, to ensuresafety during driving. For instance, if a particular applicationrequires entry of text, navigation of controls, or other activities thatwould distract the driver during operation of the vehicle, such vehiclecontrols or application controls for application interfaces can betemporarily disabled, or can be automatically transferred to a heads updisplay, or can switch to take audio vocal input from the user. In someembodiments, when the vehicle has come to a stop or is place to park,certain controls or interfaces can be re-enabled, or moved back tooriginal display location or converted back from voice input to touchinput. In one embodiment, tools provided by the vehicle site orthird-party site can provide for customization of the layout of thedisplay screens of the user interface.

The customization can include organizing or laying out system interfacesas well as application interfaces, such as those interfaces provided by3rd parties. In one embodiment, interface rules are applied to determineif the system interfaces can be replaced with third-party applicationinterfaces, while providing access to the control interfaces via theAPIs of the systems. For example, if the user wants to provide a customspeed indicator, the speed indicator must be compliant (via APIs and/ormapping) with the system interfaces so that the speed readings can bepopulated to the third-party application. In one embodiment, rules canbe integrated with or applied to the applications and system userinterfaces for when the vehicle is moving. As mentioned above, suchrules can limit interactivity with certain user interfaces while thevehicle is moving to prevent unsafe driving. In one embodiment, thecustom user interface is saved to the user profile.

The user profile may contain settings, such as selections of the userinterface components associated with the system of the vehicle, as wellas user interface is provided by third-party applications. In addition,the user profile can contain and store settings provided by the user.The settings provided by the user, as mentioned is this disclosure canalso be learned settings based on use. The settings can further includeremote access settings, as well as settings allow the user to controlvehicle components from a remote location or a remote computer. Thesetting can also include providing access to the user account to viewhistorical driving patterns, recent driving activities, the performanceof the vehicle during specific driving sessions, the performance ofspecific vehicle components, etc.

In one embodiment, the custom user interface configuration can betransferred to the vehicle. The custom configuration, as mentioned aboveis stored in the database of the vehicle manufacturer, or a databaseheld by a 3rd party that cooperates with the vehicle manufacturer toprovide cloud services. The database, in one embodiment, is a networkaccessible storage which allows access to the user to program and modifythe user interface using any computer or device having access to theInternet, including the vehicle itself or a third-party vehicle. Themethod then proceeds to operation where the custom user interface can beactivated in managed for Internet connectivity for components of thecustom interface. For example, the vehicle's Internet access protocolscan be set, or registered with an Internet provider or service providerfor the cloud services. The service provider for the cloud services canbe the vehicle manufacturer, a company cooperating with the vehiclemanufacturer, a third-party company, or combinations thereof.

In one embodiment, the method/logic can also enable local communicationwith mobile devices that may be in the vehicle. The enablement may beprovided by allowing synchronization with the computing system of thevehicle, or with the computing communications of the portable device.For example, the local communication can be paired automatically, basedon a preset pairing process where pairing keys are entered. Thisprovides for automatic settings and synchronization when the user entersthe vehicle with the portal device. As mentioned above, user interfacesassociated with applications loaded on the user's portal device can alsosynchronize to the display screens of the vehicle, as predefined by theuser.

In one embodiment, vehicle settings are saved to either a memory numberbutton on the vehicle or synced to a key fob, or accessible via aninterface or voice activation. In one example, a vehicle operatorprofile is provided to allow users to maintain their individualizedprofiles, settings and accounts for vehicles from any internet connecteddevice or be able to login to their vehicle physically in or near thevehicle by the use of a fob, thumb print, eye scan and or manual loginusing an input device that interacts with the vehicle's login system.

In one embodiment, the profile can be managed at a user account saved toa central or cloud distributed system, to manage access. Any vehicle canbe abstracted so that any user can log into any vehicle if they have anaccount that allows access to that vehicle. For instance, a vehicleowner with the role of “administrator” (e.g., an administrator of a useraccount that has a profile associated therewith or multiple/subprofiles) can create logins for his or her vehicle(s) for additionalusers such as his or her children, spouse, mechanic, and valet driveramong other applications. Logins can be created for individuals or forroles such as the role of “child” where all users with the role “child”would have the same vehicle specifications applied to the vehicle theywill be logging into. Similarly, the role of valet can be given andshared by any valet driver.

The purpose of abstracting vehicle operators from the vehicle itself isa shift from the current state of the art in which settings are vehiclespecific—each vehicle typically only having the ability to store 1-3sets of settings, to where vehicle settings are user specific and 1-nlogins can be managed through an access management system. Theembodiments defined herein allow each user to apply his or her settingsto any vehicle based on their login information in which they providetheir login and password. When a user logs into a vehicle, the vehiclewill determine locally on board and/or communicate remotely with acentral or distributed access management system to determine thevalidity of the login presented to the system. If the user's login isrecognized, the system will apply settings and use privileges to thevehicle prescribed by the login.

Logins can have “role” specific settings and privileges or settings andprivileges set only by the administrator that cannot be overridden bythe user of the login. For instance, an administrator may create a loginfor “John” their 16-year-old son. The administrator can apply settingsto John's login that John cannot override such as the maximum speed thevehicle can travel. For instance, Although the vehicle may have theability to travel at a speed of 130 mph, John's login will only allowthe vehicle to travel at a speed up to 90 mph. Additionally, every loginmay have settings that the user of the login can toggle to their likingsuch as the list of radio stations they would like pre-programmed everytime they log in to any vehicle that accepts their login.

Logins can control all aspects of a vehicle's behavior and can beattributed to individuals or roles. These settings can be toggled via anetwork connected device such as a computer, web application,smart-phone or directly on the vehicle. Administrators can decide whichsettings are locked for specific logins or roles, which are open for thelogin user to toggle and which settings are to be enforced depending onthe time of year, or time or day etc., or when a condition or event isdetected.

Login settings that can be set and remotely administered include but arenot limited to, driving characteristics (rate of speed, fuel consumptionguidelines) location based settings (GPS aided travel restrictions,travel radius boundaries, dynamically loading maps, dynamically loadingdirections, dynamically loading fuel, charge and battery service andpurchase locations etc.), time of day based use restrictions (daydriving only for example), automatic purchase settings (financialinstitution linking for automatic purchasing of fuel, charge time,batteries, car washes, etc.), fuel settings (Electric only, fuel only,hybrid only etc.), refueling routing and purchase (incentive basedre-fueling maps, incentive based refueling offers etc.) drivingcharacteristic settings (sport, comfortable, soft, off-road, highperformance, economy mode), entertainment system settings (radio memorysettings, internet access or restriction, streaming services settings),comfort & HVAC settings (climate control, seat positions, seatheater/cooler, suspension/ride settings, entry lighting, remote start,remote stop etc.) tracking/metric settings (camera/video recordingguidelines, mileage, top speed, average speed, MPG, wear and tearsettings and notifications, historical travel maps).

Automatic purchase settings can be processed in response to requestsfrom the vehicle. The request can be, for example, to transact a paymentis for one of a car wash service, a fast food service, a toll roadservice, a goods purchase service, a rental service, a lease service, orcombinations thereof.

Additionally, combinations of settings or setting profiles (such as“sport” where your seat moves to sport position for additional support,suspension stiffens, throttle response becomes aggressive etc.) can beset as well instead of individually setting use characteristics. In oneembodiment, logins are user specific, not vehicle specific, so anyfamily member can use their login on any family vehicle and the vehiclewill perform based on the metrics and restrictions dictated by the loginused to operate the vehicle.

Companies or entities can create and manage logins to company vehiclesfor delivery drivers, car washers, and mechanics among otherapplications. Each login can be configured to provide or restrict accessbased on the user logged into the vehicle. A company may only allow adelivery vehicle to travel at a maximum speed of 80 mph to limitreckless driving. A company may create a role of “local delivery only”where a driver with that login can only drive the vehicle within theirterritory. Breaches in territory travel will result in a recorded eventand notification to the vehicle administrator as well as the vehicleoperator. A grace period will be given to re-route back into thedriver's territory before more aggressive vehicle disabling mechanismsare deployed. The driver will be given visual and audio cues as to howto avoid vehicle disabling.

A dealership can grant “test drive” logins to potential customers, whichallows them to operate less than 100 mph and only within a 5-mileradius. In one embodiment, alerts or notifications can be automaticallytriggered if violations in the restrictions are detected. A dealershipmay also grant a “demo” login for instance which showcases the vehicle'scapabilities, available APPS, features and benefits. Variations of the“demo” login can be used on variations of potential buyers. A “18-24year old demo” may be useful for enticing that demographic and showcasesthe vehicle's features 18-24 year olds are most receptive to.

A valet can be given a password to login only as “Valet” which willimpose restrictions on trunk operation, vehicle speed operation, vehiclelocation notification settings etc. A recording option can be provided,which can set a recording within and around the vehicle when in thevalet mode. This way, the user can login to see what the valet driverdid while in possession the car, in case the owner feels that somethingis not correct when the vehicle is returned to the owner. Additionally,while the valet is driving the car, a notification can be provided tothe valet that will alert the valet that recording is in progress, andtheir face can be shown on the display while the valet parks the car.

A user may set the valet login to alert the user that left the vehiclewith a valet that the car has traveled beyond the allowed radius or hasreached a speed greater than 100 mph, for example. This alert can besent wirelessly to an email address, texted via mobile phone number orsent to a mobile device having a login-profile mobile applicationcapable of sharing current vehicle location, speed, fuel status amongother metrics. The last logged in user of the vehicle or vehicleadministrator can send visual, audio or auto override notifications tothe valet letting them know they need their car back, they are travelingtoo fast or even auto shut down to prevent theft.

A parent can set up a login to the family vehicle for their child thatonly allows the child to drive within a certain radius. For example thevehicle may only be used to drive between home and school. A map can beoutlined on the account management interface by a parent when setting upthe child's login to support the home to school restriction intended.

In one embodiment, a parent or company may give a child or companydriver a login that also carries a financial allowance connected to oneor more financial institutions administered through the accessmanagement and/or login management system by administrators. Forinstance, a child may have the need to re-fuel the vehicle by purchasingeither traditional fuel, battery units, and or charging time but aparent does not want to give a general credit card to the child. Theparent will set a budget for fuel purchase for the given login and thelogin will then allow the vehicle will communicate with the fuel,battery, and or charge-dispensing unit automatically using a wired orwireless communication systems funding the purchase automatically up tothe allotted budget set in the login of the vehicle.

In one embodiment, these features are useful for fleet vehicles wherecompany vehicle users currently use a corporate credit card to purchasefuel where fraud may exist in the form of using company credit cards, orcompany fuel accounts to fuel personal vehicles. The new system ensuresonly the company owned vehicle is approved to purchase the traditionalfuel, battery, charging time and also maintains metrics on which loggedin user consumed fuel and re-fueled which vehicle.

In one embodiment, a process is created so that some or allmanufacturers use the same type of login/access management system. Byway of example, any user can log into any vehicle from any brand in sofar as they have account creation access or a recognized login. Oncelogged in, each vehicle will receive and impose the login-based settingsas long as the manufacturer supports the login/access system.

FIG. 1 shows various methods a user can interact with a vehicle loginsystem, in accordance with one embodiment. The user may use anynetwork-connected device ranging from a mobile computer, mobile phone,mobile network device all connecting to a remote converged ordistributed network cloud system. The user may also interact with thevehicle login system directly on or near the vehicle. The user supplieslogin credentials to a vehicle login interface which are sent to theremote distributed or centralized user login authentication system oronboard vehicle authentication system. The processing logic receivingthe login credentials processes the data and returns an authenticationresponse to the user attempting to log in. If the authentication is asuccess, the vehicle the user attempted to log into has vehicle settingsapplied to it and the user is allowed to operate the vehicle. If theauthentication is a failure, the user is presented with a failed accessnotification on the login interface.

FIG. 2 shows two different types of users and an example of how the useris organized, in accordance with one embodiment. In this example, User 1is an administrator of a vehicle login system over vehicles he or sheowns. User 1 has the ability to add or remove logins, roles and vehiclesto his login system. Since User 1 is an administrator, he or she can addmore logins and or roles to the system to allow a family member to haveaccess to the family vehicles for instance. In this case, a familymember “User 2” is shown. The administrator has given this family membera login named User 2 and has granted two roles to User 2. User 1 mayonly want User 2 to have access to a certain vehicle and to certainroles only. User 1 may only want User 2 to have access to the vehiclefor the purposes of traveling between school and home. In this case User1 has created a role that is applied to User 2, which only allows thevehicle to travel within certain restrictions and geographicallocations.

In this example, User 2 does not have the ability to alter his or herlogin, role or vehicle since they do not have administrator access.However, User 1 can make changes on behalf of User 2. The full range ofsettings over a vehicle that applies to a given role or login is a superset of settings. User 2 may have access to a subset of settings thatUser 1 allows changes to by User 2.

FIG. 3 shows a graphical representation of an example set of settings anadministrator such as User 1 may have to administer logins, roles, andvehicles. FIG. 3 further expands the depth of settings, including butnot limited to, vehicle administration, adding or deleting users androles, vehicle global settings that apply to all roles and logins,adding or deleting vehicles among other settings.

FIG. 4 shows one sample of many potential configuration settings for agiven vehicle. In this case, User 2 has a login created for him or hernamed “CHILD”. This login contains a set of settings that may or may notbe configurable by User 2 since User 2 is not an administrator, only asubset of settings are open to him or her to alter. The drawingillustrates the settings that are user editable and admin only orrestricted. The left column lists the type of settings corresponding onthe same row on the right column. These settings are examples and may bealtered, added to, or subtracted from in different embodiments. Forinstance, fuel use settings allow an admin in this case to choose whattype of fuel the user login CHILD is allowed to use while logged intothe vehicle. Similarly, location based settings allows an administratorto draw out a map of the area the user login CHILD is allowed to travelwithin while logged into the vehicle.

FIG. 5 describes extended settings from FIG. 4. This figure describesadditional vehicle settings that are configurable by the user with thelogin “CHILD” and those that are only configurable by User one being theAdministrator. FIG. 5 also describes a subset of settings a user loginCHILD in this case is allowed to change. For example, the user loginCHILD is allowed to select his or her radio stations, streamingservices, and Internet access settings for a unified experience in anyvehicle they log into using this log in. Similarly, the user login CHILDcan access driving modes and set the vehicle mode to sport for instance.It should be understood that the example “CHILD” profile is just that,an example, and any type of user profile may be set with the definedprivileges and/or restrictions.

FIG. 6 illustrates an example of utilizing a profile of the user, toaccess cloud services 120, and a database 115, in accordance with oneembodiment of the present invention. In this example, a user may utilizea connected device 110 to access cloud services 120. Using the connecteddevice 110, the user, in this case Bob, is accessing his universalprofile settings. His profile settings may include settings that havebeen selected before in earlier sessions, or default settingsimplemented by a vehicle manufacturer, or another user such as anadministrator. In the example, the user may access particular activesettings managed by cloud services 120 which can cause Bob's profile indatabase 115 to be updated.

In one embodiment, Bob's profile can include specific settings,preferences, use history, and learned settings from earlier uses of oneor more vehicles. The profile settings defined by Bob, are thentransferred by cloud services 122 one or more vehicles utilized by Bob.For example, if the user wishes to utilize his regular everyday car, theprofile settings may already be stored on the vehicle. If the userwishes to utilize a different vehicle, such as a friend's vehicle, arented vehicle, a shared vehicle, a temporary vehicle, a loaner vehicle,a test drive vehicle, a company vehicle, etc., the user's profiles canalso be transferred to that vehicle.

The user profiles can include standard settings that may be set at thevarious vehicles, or custom settings that can be selected for the userbased on learned settings over time by use of various vehicles. In oneembodiment, the user profiles are continuously updated and store to adatabase 115, which is accessible by cloud services 120. Database 115may include data storage, such as cloud storage, data center databases,distributed databases, local storage on vehicles, network storage, andthe like.

FIG. 7 illustrates an example of a user (Bob) that may wish to utilize acar 200, in accordance with one embodiment of the present invention. Forexample, the car 200 may be a shared vehicle, such as those commonlyshared in urban cities. Shared vehicles are those that belong to acompany and where the company provides accounts to users to access thevehicles for specific trips, specific times, periods of time, etc. Usersthat share those vehicles typically park the vehicles at differentlocations throughout an urban city. Users wishing to find a vehicle touse can access an application or website having access to an Internetconnected application to find the vehicle closest to the particularuser.

Once the user has located a proximate vehicle, such as car 200, the usermay approach the vehicle so as to utilize the vehicle 200. In oneembodiment, when the user approaches the vehicle, and comes in closeproximity to the vehicle as detected by the geo-location of the usersmobile device, a pairing request can be detected. The pairing requestmay be triggered once the proximity zone of the car 200 and theproximity zone of the user substantially or partially overlap. Theproximity zone's may overlap when the user comes in close proximity tothe vehicle, such as within a few feet, within a mile, or the user hastouched or bumped the vehicle.

The pairing request may be automatically sent by the users device tocloud services 120. The pairing request can include sending the model ofthe vehicle 200, which may have been obtained by the users mobile devicefrom the vehicle 200 directly. In the illustrated example, the pairingrequest by the users mobile device can include identification of thevehicle that the user has come in close proximity to. A pairing module170, can then communicate with a mapping engine 118 that determinesinformation associated with car 200.

An automaker database 116 can include data regarding a plurality ofvehicles, including standard user interfaces, configuration interfaces,and other information necessary to provide user Bob with a custominterface for vehicle 200.

The mapping engine 118, in this example includes a map or thatcommunicates with the automakers database to identify the settings,applications, APIs, or modules that allow integration of Bob's userprofile from the user profiles database 160 so that Bob's profile can besent to car 200. In the illustrated example, the mapping engine, the ofthe mapper, will obtain Bob's profile 160 for cloud services and obtainvehicle information for the user interfaces of the vehicle desired foruse by the user.

The mapping engine 118 will the transfer Bob's profile to vehicle 200.At this point, the user, Bob, can be provided with an interface on amobile device to allow access to the vehicle. The user interface caninclude a plurality of screens with instructions, check information,cost information, billing information, etc. As illustrated in FIG. 7,the users mobile device can provide various notifications, such asidentifying to the user that the user standing next to a blue model M7from maker C. The user interface can ask Bob if Bob wishes to pairsettings to the specific vehicle 200. If Bob desires to actually utilizethe shared vehicle 200, the pairing request may be initiated asmentioned above.

FIG. 8 illustrates another embodiment where the user Bob has utilizedhis mobile device 100 a to define or access a plurality of settings. Inone embodiment, the user may register 214 with a car sharing service,such as via a user interface or application having access to theInternet and the company providing the service. Cloud services 120 canthen provide access to the profile database 160 where Bob's profile maybe stored. The profile 160 may be accessible to 3rd parties, such as carsharing service.

Also shown in cloud services 120 is the car database 116/115. The cardatabase can then be provided with information from the car sharingcompany 210 that identifies the cars that the company owns and that areshared with the service. The car data including assigned IDs to thevehicles and cars can be stored in the car database 116/115. Additionaldata can be supplemented from vehicle manufacturers 212. The cloudservices 120, in accordance with one embodiment, can include logic forprofile identification for vehicles 224, logic for proximity detection222, user request logic 220, and other managing logic for receivingrequest from users, managing databases from a car sharing database,managing data from vehicle manufacturers, and receiving request tomanage profiles an axis vehicles.

As illustrated, when the user Bob approaches the vehicle 200, the Bob'smobile device 110 a can identify the closest car, which may be car A. Inthis example, Bob is identified to be proximate to the car having an ID1528 ABC. In one embodiment, when the user comes in proximity to the car200, the car can beep or light up when enabled, it can open the doors toallow the user to access the vehicle when the logic has paired the userto the vehicle, the profile of the user can be transferred to thevehicle, the use of the vehicle is managed by the user's online account(storing historical use data and any billing information), automaticpayment for use can be made from predefined payment arrangements storedin the profile, and use of the vehicle can be restricted to predefinedrules, based on the profile. Accordingly, the profile database 160 caninclude both profiles of the user, such as user settings, as well asprofile restrictions that may be set by the car sharing service.

FIG. 9A shows one example process for utilizing user profile settingsfrom a registered user and utilizing settings of a shared vehiclenetwork, in accordance with one embodiment of the present invention. Inthis illustration, operation 300 receives the user profile settings froma registered user of a shared vehicle network. The registered usersprofile can be obtained from a cloud services profile, such as theprofile used for a number of vehicles which may be in or outside of theshared vehicle network.

In another embodiment, the profile may be the profile set by the sharedvehicle network, based on the service contract entered by the user. Inoperation 302, vehicle IDs for each vehicle assigned to a shared vehiclenetwork are received by cloud services 120. Cloud services 120 willtherefore maintain a user database 160 with a plurality of userprofiles.

Cloud services can also maintain a vehicle inventory database 310 forthe shared vehicle network. Servers 350, which operate cloud services120, and therefore managing access database 160 and 310, as well asprovide logic for providing access to vehicles, unlocking vehicles, andtransferring user profiles to specific vehicles. In operation 360, theservers 350 may receive a request to locate a vehicle on a map from acomputing device. The request may be provided with reference to theuser's current location, using GPS or the like. The request is thenprocessed by servers 350, and servers 350 communicate the forward a listof available vehicles proximate to the user or for the users identifiedarea in operation 362. In operation 364, a selection request is receivedfrom the user for a specific vehicle and a reservation is made for theuse of the vehicle for a set period of time.

In operation 366, a command is sent to the vehicle the signal alert whenthe user is detected to approach the vehicle within a particulardistance, notifying the user that the vehicle is the vehicle that theuser reserved. This provides for a method of allowing the user to easilyidentify the vehicle that the user reserved. For example, if the user isinstructed to go to a specific parking lot to identify the vehicle thatwas reserved, the user would have a difficult time identifying whichvehicle it is that the user reserved. However, by allowing cloudservices to signal to the vehicle to sound the alarm, turn on a light,beep, for make any other identifying gesture, the user can easilyidentify the vehicle in the parking lot.

In operation 368, a user interface is provided to the user's mobiledevice that will provide a notification to the user indicating that theperson/user has arrived at the vehicle. In operation 370, the usersprofile is transferred to the vehicle. The transfer of the profile willallow the settings of the user to automatically be set in the vehicle.The settings can include, for example, temperature, radio settings, seatsettings, meter settings, air settings, etc.

In operation 372, the settings that are made by the user when in thevehicle or adjustment settings can be sent back to the user profile.Thus, when the user offering the vehicle and making changes to his orher profile, those changes can also be communicated back to the profiledatabase in cloud services 120. This provides for a continuous feedbackloop over time, to allow the users profile settings to be managed andmaintained current to the users best liked preferences. The operationthen proceeds to B in FIG. 9B.

In operation 374, it is detected that the user has completed use of thevehicle upon some user entry at a computing device. The computing devicemay be computing device of the vehicle, or a mobile device. The entrycan be, for example, the user logging out of the vehicle indicating thatthe user has terminated use of the vehicle. At logout, the vehicle'soriginal profile settings will then be returned, and the users customprofile settings will be terminated.

In operation 378, a report sent back to the server regarding the use ofthe vehicle and the charges to the users account for the use. In oneembodiment, the use reporting can occur continuously while the user isdriving vehicle. In operation 380, the drivers session log can be saveduser profile, keeping a history of the user's travels. In operation 382,survey data can be requested of the user regarding the vehicle use.Because the user was utilizing a shared vehicle, feedback from the usercan be helpful to potential future users that may want to rent orutilize vehicles from the same company.

The user may be provided with options to publish likes and dislikes orcommentary to a social network 390. Ratings can also be transferred torating companies, such as those that allow internet users to view usercomments, reviews, complaints, etc. The social network 390 can allow thedata to be open data 394, or data that is shared with friends 392. Inoperation 384, problems with shared vehicle can be reported to thevehicle network to allow repairs before making the vehicle available forreuse. Cloud services for the shared vehicle network can then be updatedin cloud services 120. For example, if the vehicle has been identifiedas having some mechanical malfunction, the cloud services can updatethat vehicle as being out of service, so that discovery of that vehicledoes not cause users to access that specific vehicle that may be out ofcommission.

FIG. 10 illustrates a user (Bob) entering the vehicle, such as a sharedvehicle 200, in accordance with one embodiment of the present invention.In this example, the user has been identified by the vehicle, such asusing a camera 402. The camera 402 may use face detection 406 toautomatically identify the user, and set the users preferences andsettings for the vehicle automatically. In some embodiments, this allowsverification that the user driving the vehicle 200, from the sharednetwork, is the driver that unlocked the vehicle from a remote location(such as a mobile device). In this example, the vehicle 200 may alsoinclude a plurality of cameras, such as cameras 404, 408, 410, 412, 402,etc. Any one of these cameras can be accessed from a remote location, ifthe user's profile provides access, or the privacy setting allows suchaccess.

These cameras can be used to detect and monitor the exterior portions ofthe vehicle as the vehicle drives around, as well as interior portionsof the vehicle. These cameras can be used by the vehicle sharing companyto monitor the status of the vehicle, and the location where the vehicleis parked. In one embodiment, the user who has rented the vehicle canset a privacy setting to disable certain cameras. In one embodiment, aspeaker 420 can be activated to allow the vehicle to speak andcommunicate with the user. Vehicle electronics and logic 400 can be incommunication with cloud services 120.

Cloud services 120 can also be in communication with user profiles 160.In one embodiment, the user profiles 160 can also include specificprofiles for registered users. In one embodiment, the registered userscan include a family of users. A specific family can have a number ofdrivers or users that have been registered with a service. For example,the database can include users ABC123xi (such code is only an example,and any form of ID/code can be used), and the users can include aparticular family or group of people. The group of people can also be agroup associate with a company, a sharing service, a group establishedfor a particular event, or other types of groupings. The vehicles cantherefore be monitored for use by the specific users in a particularfamily or group. In one embodiment, the particular family and groups canbe associated with their own profile history settings, which includedata from their previous uses.

In one embodiment, FIG. 10 illustrates a process utilize to communicatebetween vehicles, users, and cloud services. In operation 450, a vehiclewith communications is provided with cloud services. The cloud serviceswill be in account, software, or interface that allows communicationwith cloud services 120. In operation 452, the user in the vehicle maybe detected, and the face of the driver or other biometric data can beused to identify the specific user sitting in the car. The detection ofthe user can, in one embodiment be enabled or restricted based onprivacy settings desired by the user.

In operation 454, the user may be identified and the users profile canbe automatically retrieved from cloud services and the user profile 160.The preferences settings for the user can be identified from thedatabase in operation 456, and the settings can be applied in operation458. The settings can be applied to the vehicle for the identified user.When the user terminates use of the vehicle, the settings can't bedeactivated, or return to a neutral setting.

FIG. 11 illustrates an example of particular types of settings that canbe set, or recorded, or accessed, in accordance one embodiment of thepresent invention. In one example, cameras 480 can be provided asoptions for access by the user. The cameras can be accessed to viewhistorical uses by the user, or can be access to view current and livevideo of the vehicle. For example, if the user has rented a vehicle fora period of time, and parked it in a specific location, the user canmonitor the vehicle from a remote device connected to the Internet.

Record settings 482 can also be set by the user, the vehicle provider,or cloud services. A plurality of recording options and access can beset or adjusted by the user from a remote location. Remote access 484also provides the user with options to control specific features of thevehicle. The control the vehicle can be set for a period of time whenthe users profile is associated with the vehicle.

In a car sharing environment, the remote access of the vehicle can beenabled during the period of time when the user is assigned or the usersaccount is assigned to that vehicle. In examples where the user owns thevehicle or is more tightly connected to the vehicle, the remote accesscan be provided by entering axis control information, credentials,passwords, usernames, and biometric data or combinations of one or more.

In still other embodiments, user interfaces are provided to provisioncustomized data regarding available charge station locations. In oneembodiment, users having other devices, such as smartphones or portableelectronics can obtain data, which can be shared with other userinterfaces. The sharing can be by way of a sync operation, that can beautomatic when the user enters the vehicle or on demand by the user. Inother embodiments, the application or program running on the userportable electronic device can continue to execute the processing, whileallowing the display of the vehicle to show all activity on the display.For example, if the vehicle electronics are not capable for processingan application or access a cloud service, the portable device can act asthe agent for the vehicle electronics. In one embodiment, the displayand I/O of the EV simply acts as a passive interface, while theprocessing or accessing to cloud processing is done by the user'sportable electronics (e.g., smartphone or the like).

In some embodiments, the user's portable device is already programmedwith access codes, passwords, etc., so the user may wish to use theportable electronics instead of having to program the vehicle. This isimportant when users share a vehicle. If users share a vehicle, one usermay have the electronics programmed to their likes or dislikes. Byallowing programming, data settings, etc., to be shared or synced (e.g.,temporarily or not), users can more easily share vehicles, while keepingthe settings that the user is used to having.

In still another embodiment, allowing the user's smart phone or portableelectronics to sync with an EV, users of rental cars can more easilystep into cars with pre-programmed settings. Thus, users thattemporarily use vehicles need not worry about programming the car'ssettings upon entering the car, but simply sync with the vehicle toallow the vehicle to run display, IO and services based on the customsettings of the user's portable device.

This processing that allows users to sync a vehicle with a user's customsettings stored in the user's portable device can also have applicationto car sharing environments. In big cities, companies allow users tolocate vehicles in a proximity to their current location, and simplyenter the vehicle using their membership code. In addition to providingusers with access to the vehicle, the user/driver's settings can besynced to the vehicle. This can include settings of the seats, themirrors, the temperature, the radio stations, and the Internet apps todisplay on the car's display, etc. Custom information, such as prioruses of the car, cost for driving, etc., can be displayed on the car'sdisplay, via the sync data from the user's portable device. The syncdata can be obtained at any time, such as by using the user's portableInternet link, etc.

In one embodiment, a user's EV or non-EV vehicle can be in communicationwith cloud services, and the cloud services can be interfaced with datafrom various entities that provide power for the grid, provide chargingunits (CUs), provide discounts to charge at particular CUs, geo locationservices, mapping services, live traffic data, etc. The user of the EVcan communicate with the vehicles electronics via a display unit and itsassociated electronics, can provide input via touch or voice, canrequest data regarding routs to local charge stations, cost estimates atthe various charge locations, how crowded the charge stations are at thevarious locations, etc.

The cloud services 120 are also accessible via a computer that hasaccess to the Internet, a smart device (e.g., smart phone, tablet,etc.), etc. Thus, data can be acquired from various sources and data canbe consumed by various sources. The data that is acquired, shared oraccessed can be launched on the user's device and then transferred toshare in real-time with the display and/or electronics of the vehicle.Thus, a unified access display can be customized to the user, regardlessof the vehicle that the user chooses to drive. This is in contrast tocurrent models that customize settings for one vehicle owner or owners.

In one embodiment, the user's settings are seamlessly transferred to thevehicle the user chooses to drive. This is especially useful for caseswhere a user drives many cars, but wishes to keep his settings constant.Settings can include cloud services, or local settings such as seatpositions for the size of the user, mirror positions, radio stations,weather stations, history of routs taken, favorite locations to visit,etc. The application that allows syncing of a user's settings on aportable device to the vehicle electronics is especially useful for carsharing applications, which is common in large cities and may expand inthe future. As car sharing increases, it is most useful to allow a userto save his/her settings in their mobile device, instead of relying onthe fixed settings of the vehicle. In another embodiment, it is alsopossible for a user to type in their universal login code (e.g., username/password) into the car display, and all of the user's settings aretransferred to the vehicle while the user is driving the EV. Once theuser stops using the EV, the car can go back to the normal mode foranother user to login. The data regarding the user's settings would, inthis embodiment, be saved in the cloud.

In one embodiment, user interfaces of a mobile device can share datawith the vehicle's display and native apps. App unification allows EVsystem to display APPS on the user's smartphone device in an opt-in PAIRmode. In one embodiment, this allows one person to enter another's EV,share apps on the EV display while in the EV, and when the person leavesthe EV, the Apps de-pair. This auto-sync facilitates sharing of data andalso allows users to unify their settings across any number of vehiclesthe user may drive.

In one embodiment, the synchronization will enable users to universallytransfer settings from portable devices to electronics of a vehicle. Insome embodiments, the vehicle that the user wishes to drive is not hisvehicle. For instance, the vehicle may be a friend's vehicle, a rentedvehicle or a shared vehicle. If the user has programmed settings in hisor her device, the settings that are useful for the vehicle will betransferred to the vehicle. Settings can include travel speedrestrictions, car seat settings, mirror settings, remote access to homecontrols (e.g., lighting, garage doors, etc.), radio settings, satelliteradio settings, internet settings, etc. In some cases, only somesettings are directly transferrable. In other embodiments, a databasecan be accessed to find a translation metric. The translation metric caninclude mapping tables that allow for settings to be transferred betweenfunctions of one vehicle to other vehicles. In one embodiment, vehiclemakers can upload their translation metric for each model and themapping tables can be used to provide the sync operation.

FIG. 12 describes a system in which a user interacts with a model viewcontroller software environment 1800 useful for processing APPS usingAPIs 130 on vehicles with vehicle operating systems 129 capable ofprocessing computer code. The APPS can execute profile retrieval,updates, and sync operations. The model view controller paradigm 1800shows basic interaction, control, processing, and updating of datauseful for manipulating and viewing resulting actions by to vehiclerunning an APP in such a system. Such a system useful for running APPSon vehicle operating systems will accept inputs by a user 121, cloudservices 120 via data streams, vehicle systems feedback and data streams1812 used by a controller 1804 that may constantly poll electrical,capacitive and physical sensors, and input streams to detect ifinteractions 1808 such as network passive updates, network activeupdates, user touch, user speech, user input, user selection amongothers has been triggered.

Each input 1804 will then trigger manipulation of the system's model1802 portion of the APP software paradigm thus invoking stored routineswithin APPS 104 which then in turn interact with the vehicle's APIsystem 130 built upon the vehicle's operating system 129. Depending onthe app presented to the user 121, the input may trigger stored routinesor functions on APP software or operating system level restricted storedroutines or functions.

After the processing of stored procedure code is manipulated witharguments provided by the controller 1804 inputs, visual and or sensoryresults are presented to the user in the view 1806 portion of the modelview controller paradigm. These sensory outputs, data streams,electrical signals may all be translated as additional options, results,dynamic updating, audio or visual graphical user interface changes 1810on any of the user's connected display devices. The user will noticethese results visually or audibly but may also feel or detect changes inthe vehicle's mechanical systems. Updates from the model 1802 may alsobe used to toggle vehicle settings 1814 which in turn may invoke changesin the vehicle's physical, mechanical and electrical systems 128.

Finally, the system controller 1804 may receive additional updates fromthe vehicle systems affected or additional user 121, cloud services 120,vehicle systems feedback inputs 1812 to re-engage the user in a cyclicalfashion. If no inputs are sensed, the system's controller will continueto poll its electrical and data I/O systems for input on a continuousbasis.

The model view controller paradigm 1800 described is one example of thesoftware input output lifecycle that may be used to invoke, manipulate,process, update portions of computer readable code such as APPS 104using an intermediary API 130 to communicate with the vehicle'soperating system 130. However, APPS 104 may be run on physically wired,wirelessly connected or remote devices having processing abilities totranslate the computer readable code in APPS into actionable invocationson one or more vehicles in order to facilitate or utilize the vehicle'selectrical and mechanical systems in prescribed or customizablefashions.

FIG. 13A describes how vehicle on board computer with input outputsystem 1900 useful for accepting input, processing input and displayingresults in conjunction with stored computer readable programs orfunctions in the forms of APPs 104 may be structured. Although system1900 describes one way to provide vehicle on board computing power torun APPs 104, the arrangement of the vehicle computer 1906 may bealtered or arranged in differing fashions with differing connectionrouting in order to achieve the same. In this example, vehicle on boardcomputer 1906 may be comprised of components such as the networkinterface 1910, memory 1912, a central processing unit 1914, an inputoutput buffer useful for streaming data 1916, storage 1908 having theability to store computer data in long term or short term fashion usefulfor stored computer code procedures in the form of an operating system129, intermediary stored procedure code in the form of APIs 130, storedsubsets of computer code procedures APPs 104 interacting with API 130 asan intermediary to the operating system 129.

In this example, the vehicle computer 1906 has the ability to transmit,receive and process information using wired or wireless connections. Onesuch wireless connection is provided by a wireless data sending andreceiving antenna 1928 connected to a network interface 1910 useful forpairing with and communicating data with portable or stationary wirelessdevices which may or may not be part of a network 1902. Such wirelessdevices include but are not limited to wireless displays 210 b, portablesmart phones 210 a, portable computers, 210 c and even stationaryobjects, structures, buildings, toll bridges, other vehicles etc. Thevehicle's network interface 1910 through antenna 1928 may alsocommunicate with cloud services 120 to receive instructions from aremote location that invokes stored programs such as APPs 104 on thevehicle's computer.

The vehicle may also send and receive data wirelessly in order toestablish a connection with a peer-to-peer ad-hoc network. Invocationsmay result in output data streams interpreted by wireless devices 210 b,210 a, 210 c as well as wired devices such as wired displays 210 d orvehicle integrated display devices such as windshield heads up projecteddisplay or integrated glass displays 210 e. All data streams generatedby APPs 104 stored on the vehicle's computer may also be triggered bywired devices such as vehicle sensors 1918, vehicle electrical systems1920, vehicle electrical systems 1922, engine control systems 1924,vehicle diagnostics systems 1926, user input as well as environmentalinput.

A user and or vehicle may find system 1900 useful in one example, wherethe user drives the vehicle past an electronic toll bridge where a feeis required to pass the toll bridge. The vehicle's computer willcommunicate wirelessly as it passes the stationary structuretransmitting and receiving information with it as it drives by. Theuser's vehicle may have an APP 104 installed on the vehicle computer1906 that can process the input using the computer's wireless antenna1928, network interface 1910, input output system, 1916 automaticallyresponding to the toll bridge with payment information. Once the paymentis received and processed, the APP 104 receives information from thestationary wireless toll taking device which is then stored eitherlocally on the vehicle's storage 1908 or remotely using cloud services120. The results of the transaction are then sent via data stream fromthe compute code running on the APP 104 to a display device(s) where theuser can visually confirm that the toll was paid, accepted and show theuser's remaining balance all through the GUI displayed for APP 104.

FIG. 13B describes one example of how stored data and functiondeclarations may be compiled to provided intermediary access to avehicle's computer controlling vehicle systems 1950. Such routines, dataand functions may be arranged in such a way that limited access is givento third party code on APPs 104 to manipulate certain unrestrictedoperating system functions and vehicle systems. Such a method ofproviding the intermediary allowed stored function set to third partycode can be referred to as an API 130.

In this example of an API 130, computer readable code is arranged insuch a fashion that the type of API is described and in this case, anAPI that allows third party control of the vehicle's HAVC system isdeclared. A declaration may be useful for reserving the vehicle'scomputer long term and short-term memory in order to run storedprocedures. The shown declaration 1954 describes an example set of datathat may reference memory locations and their contents. The contents ofthese memory location may be modified by stored procedures 1956 orfunctions.

This HVAC API 130 has the ability to store data relating to thevehicle's temperature, status, target temperature, split zone temperate,data from electrical and mechanical sensors, calendar dates, errorinformation among others. Invocable functions 1956 are the methods bywhich a third party APP 104 may manipulate data 1954 on board acomputer. Free access is not given to the restricted data on a vehicle'scomputer, thus a structured method or methods are described for user bythird party APP developers.

These functions 1956 that may or may not take arguments in order toexecute may include functions in the example HVAC API that updatetemperatures for both the left and right or given zones of the vehicle,toggle are conditioning, allow visual skins on the APP GUI, manipulateschedules and displays etc. The HVAC API 130 described is one example ofhow one API can control one vehicle system. There may be variations ofthe APIs for multiple vehicle systems or one superset API that allowsaccess to all of the vehicle's systems through stored procedures ormethods.

FIG. 13C describes a set of computer readable and executable code 1970that can be compiled together by a third party APP 104 developer in theform of an APP. The APP 104 uses structured programming languages toexecute stored functions allowed by the vehicle's system API 130. Inthis example, the APP is a third party HVAC app that allows a GUI to bedisplayed to a user giving them the option to adjust the temperature onthe left or right side of the vehicle up or down. In this case, theAPP's GUI has provided a data stream to the APP letting it know that theuser has selected to set the temperature on the left side of the vehicleto 80 degrees and the right side of the vehicle to 76 degrees.

The APP 104 will then use functions available from the vehicle's API 130to manipulate the data on the vehicle's storage system which in turnwill be electrically polled by sensors, data streams etc. to manipulatethe vehicle's electrical and mechanical HVAC systems. The user willnotice the result visually by the data provided by the APP to the GUI aswell as environmentally as the temperature is changed in the vehicle.

FIG. 14 describes the stepped flow of events 2000 as a user interactswith an APP 104, in this case, an HVAC APP 104. The GUI shown for APP104 describes the first step 2002 where a user physically interacts witha sensor, screen, voice system etc. polling to see if an input has beenreceived. The user's input in 2002 has been interpreted by the app toraise the temperature on the left hand side of the vehicle to 80 degreesand maintain the temperature on the right hand side of the vehicle at 76degrees. This input invokes step 2004, which calls a stored function onthe APP 104 that is API 130 allowable with arguments. The storedfunction may invoke other helper or associate functions within the API130 in step 2006, which all in tern invokes restricted computer readablecode at the operating system and or kernel level in step 2008. Theseinvocations will then in turn command mechanical and or electricalsystems in step 2005 in order to achieve the requested response in step2002.

The results of the commands on the vehicles systems are based back tothe vehicle's operating system or kernel level in step 2012 which thenupdates data on the API 130 in step 2014 that the APP 104 is polling,such as updating the display to show the resulting temperature in step2016. The results of a function that is invoked at the API 130 levelupdating the display produces a data stream translatable and displayableby the vehicle's screen showing the APP 104's GUI in 2018.

FIG. 15 describes further example ways an APP 104 may take, process andproduce results 2100. FIG. 14 shows a way to interact with an APP 104locally but a vehicle computer system may relay data, inputs andinformation to the APP while connected to a wide area network, localarea network, cloud process 120 or private cloud. A remote action toinvoke change on an APP 1808 may be initiated via a network and pass tothe APP running on the vehicle 160 using the vehicle's antenna 1928 orwired interface. An APP 104 running virtually on a network or cloudservices 120 may also take input remotely and process the resultsaccordingly.

Some of the inputs and results 2102 that an APP can take and producelocally or remotely include but are not limited to the set 2104 that canreceive an action, react to an action, control an action, manipulatedata models, report changes to a view or GUI, record events orincidents, learn the types of requests being submitted, learn the timesof request being submitted over time, learn the days of the year therequests are being submitted over time, generalize and interpretrequests, assume user intent in order to automatically invoke changes,automatically and pre-emptively act on behalf of a user, fine tunelearned user behavior etc.

The learned behavior (e.g., learned settings that provide for automaticprogramming) can be assigned to particular applications, particularsub-features of applications, to particular native system features ofthe vehicle, or combination of one or more thereof. The learned settingscan also be managed via an interface, which shows to the user settingsthat have been learned and provides the user with options to modifylearned settings.

The modifications of the learned settings can be made via the vehicledisplay or any other device having access to cloud services. The learnedsettings can also be communicated to the user via notifications. Suchas, “We noticed you like your truck temperature at 3 pm to be 60degrees? Please confirm,” or “We noticed you like your car temperatureat 8 am to be 75 degrees, this will be preset for you automatically,” or“We have detected your favorite settings, please login to your accountto see settings we have programmed for you or make updates,” or othersimilar notifications via the vehicle or to any connected device overthe Internet.

In other cases, notifications may not be sent. In some cases, thesettings will just occur automatically. In some examples, notificationscan be provided with a link or access to a user interface of anapplication. Via the application, the user can manage, set, control orview any aspect of the connected vehicle. In some cases, the settingscan be manually adjusted by the user way from the auto settings. In suchcases, the manual setting can be learned and can be provided moreweighting since the user took the time to correct an auto setting. Thus,various levels of weighting or importance can be given to learnedsettings. In other embodiments, the learned settings can be comparedagainst learned settings of other vehicle owners having access to cloudprocessing. Using data from these different user profiles, learnedsettings can be obtained or generated.

Generation or analysis can be by way of overlap processes, clusteranalysis algorithms, Connectivity based clustering, centroid-basedclustering, clustering model most closely related to statistics is basedon distribution models, cluster validation, density-based clustering,KNN/profile similarity, collaborative filtering, content-basedfiltering, hybrid recommender systems, mobile recommender systems,cross-sectional analysis, similarities in particular data types orsettings, concentration in similar settings by particular demographics,and other similarity analysis calculators and aggregators. Thesesettings can then be recommended to the user or can be automaticallyadded to the profile. Recommender systems can the user the analyzed datato generate the custom recommendations for settings to users' profiles.

FIG. 16A describes an ecosystem where an APP 104 in conjunction with avehicle API 130 may work together to make assumptions, make decisionsand take actions 2200. API and APP code together can be arranged in sucha fashion that creates an assumption and reasoning logic module 2216.This Assumption and reasoning logic module can take inputs from varioussystems and data streams including but not limited to GPS 2206,calendars 2208, traffic conditions 2204, local news 2202, past data ofuser behavior and interaction 2210, vehicle diagnostics 1926, userpreferences 2214, user login profiles 506, environmental interpretationsby sensors 2212, marketing deals 2224 among others. These inputs can belocal and physical or remote and abstract via a network. The assumptionand reasoning logic module 2216 compiles data from these sources toinvoke decisions and actions on a decision and action engine 2218.

This decision and action engine 2218 has the ability to execute on whatthe assumption and reasoning logic module has determined needs to bedone. The decision and action engine has the ability to produce alerts,action recommendations, both local, on screen, audibly, visually orremotely on a remote display device 210 a-e using a data network. Thedecision and action engine 2218 also has the ability to change vehiclecontrols automatically on behalf of a user without user action based onassumptions made by the assumption and reasoning logic module 2216.Additionally, the decision and action engine has the ability to requesta decision from the user preemptively in order to change vehiclecontrols. In this way, a user can approve or decline the action.

This may be achieved locally or remotely requiring input from a user toproceed. For instance, the assumption and reasoning logic engine hasdetermined that the user may want to have his or her car automaticallystarted at 7:55 am because the user typically starts the car at 8 am.Starting the car at five minutes early will allow the system to heat thevehicle to the user's typical liking. However, the assumption andreasoning logic may have only reached a level of confidence of 75% where80% confidence is required to act without user input. Thus, the system,being only 75% sure that the car should be turned on will automaticallysend the user an alert or recommendation requesting a decision onwhether or not to turn the vehicle on (or perform a certain recommendedaction that have a confidence score or level above some threshold). Oncethe user 121 provides an decision remotely on their remote device 210 a,the decision engine 2218 updates the assumption module 2216 so that itcan augment its assumptions for an updated level of confidence on thenext action trigger. These actions by the user automatically andcontinually update the assumption and reasoning logic module 2216 inorder to fine tune the level of confidence on acting without user inputand learn the user's behavior for future decisions.

In one embodiment, a method for processing information associated with avehicle is disclosed. The method includes receiving a plurality ofactions set at the vehicle over a period of time. The actions can bereceived from a server or services of a provider. The method includesupdating a history profile for a user account of the vehicle for theplurality of actions. The history profile includes metadata for each ofthe plurality of actions. The method generates confidence scores foreach of the plurality of actions in the history profile and generatingone or more action recommendations that can be accepted forimplementation by the vehicle. For actions having confidence scores thatexceed a threshold, the method sends the one or more actionrecommendations to the user account associated with the vehicle. Theaction recommendations include an accept or decline option that can beset via the user account to cause data to be received indicative of theoption. For action recommendations that are accepted, the methodincludes setting a time to send a programming instruction to the vehicleand sending the programming instruction to the vehicle to cause thevehicle to programmatically perform a programmed action to implement atleast one of the action recommendations. In one embodiment, the actionrecommendations are vehicle settings.

In some embodiment, the metadata of each action includes a record of atime and date of each occurrence and for actions that show a repeatingpattern of occurrences will have an increased confidence score. Thethreshold is predefined to require a set number of occurrences of theactions to occur so that the repeating pattern is identifiable.

In some embodiment, confidence scores are increased for actions thatreoccur multiple times at about a similar time and date, and theconfidence scores are decreased for actions that do not reoccur multipleat about the similar time and date or occur at dissimilar times anddates.

In some embodiments, increases in actions that reoccur multiple times atabout a similar time and date have a repeating pattern that isindicative of a likelihood that the action recommendation will beaccepted.

In some embodiments, the actions set at the vehicle are selected fromone or more of setting a temperature of the vehicle, setting a windowdefrost mode in the vehicle, heating a seat or seats of the vehicle,setting an emergency signal of the vehicle, setting an emergency signalfor help, setting a restriction or enabling a feature for the vehicle,disabling the vehicle, selecting an audio setting, making a reservationfor service, reporting an error in the vehicle, setting a position ofmirrors of the vehicle, setting to open or crack windows upon reaching atemperature, setting notifications for recharging a battery if thevehicle is an electric vehicle, setting reminders to charge uponreaching a predefined battery state if an electric vehicle, settingparameters to identify nearby charge stations if the vehicle is anelectric vehicle, setting advertisement settings allowed to be displayedvia a screen of the electric vehicle, setting maps data, settingcommunications data, setting navigation data, setting display settingsdata, setting customization of display applications on the screen of thevehicle, setting suspension parameters for the vehicle, setting autolock/unlock controls of the vehicle, activating an alarm, settinginstructions to receive video feedback from the vehicle upon detectionof alarm conditions, setting to call for help when an accident isdetected, setting time of day on vehicle clocks based on local time;setting navigation parameters in the vehicle, setting preferred radiostations, setting sensitivity of collision detection sensors, settingsensor programming, or combinations of two or more thereof.

In some embodiments, the method may include receiving sensor data fromthe vehicle. The sensor data is associated to particular ones of theplurality of actions, the sensor data being saved to the metadata of therespective actions in the history profile.

In some embodiments, the sensor data includes one or more of actualsensed temperature, geo-location, speed, vehicle condition, occupantidentification, number of occupants sensed, biometric detection of anoccupant in the vehicle, proximity of surrounding vehicles or obstacles,voice data, video data, touch data, gesture data, surrounding vehicleshared sensor data, or at combination of two or more thereof. In oneexample, for sensing occupants, if 3 people are sensed at 8 am everyweekday, the kids programming is started—taking kids to school. In oneembodiment, kids movies or shows are started or queued up for viewing,temperature setting for the rear are set as likely desired. This, andother action settings can be set to occur, or occur if accepted via anaction recommendation.

The action recommendation can take on many forms. For example, theaction recommendation can be sent to a device directly, to an email, toan account, to a web account, to a profile, etc. The user can thenselect to accept or decline certain action recommendations. The actionrecommendations can also be queued up, so that a user can handle two ormore at one time, such as when the user is logged into their account.Queuing up recommendations, such as in an in-box of a user account canprovide for a less obstructive means of getting the user's attention.

In some embodiments, the confidence score for an action in the historyprofile is increased for actions having repeat occurrences while havingsimilar sensor data present in the metadata of the actions, or theconfidence score for an action in the history profile is increased foractions having repeat occurrences and having same sensor data present inthe metadata of the actions

In some embodiments, a method includes, for particular sensorsassociated with particular actions, making the action recommendationinclude, sending data to populate a user interface of a computing devicewith a control to accept or decline the option, the data sent is via anetwork connected to the Internet. In one example, the computing deviceis one of a vehicle computing device, or a mobile computer device, or atablet computing device, or a smart phone computing device, or aninternet terminal computing device, or a non-portable computing device.In one embodiment, the user interface can be a simple text message, anicon or symbol message, a full GUI, a picture, sounds, words, audio,music, or combinations thereof.

In some embodiments, the data is sent to the user account, the useraccount being accessible over the Internet.

In some embodiments, when the sensor is a temperature sensor and theaction is inputting a heating or cooling setting at the vehicle, theaction recommendation includes, and sending data to populate a userinterface of a computing device with a control to accept or decline theoption, the data sent is via a network connected to the Internet. In oneexample, the computing device is one of a vehicle computing device, or amobile computer device, or a tablet computing device, or a smart phonecomputing device, or an internet terminal computing device, or anon-portable computing device. In one example, the data is sent to theuser account, the user account being accessible over the Internet.

In some embodiments, the heating or cooling setting includes one or moreof activating a window defrost setting, or activating a heating setting,or activating an air conditioning setting, wherein the actionrecommendation for the heating or cooling setting at least in part usesweather forecast data obtained from the Internet for a predictedgeo-location of the vehicle.

In some embodiments, a method can further include receiving temperaturedata from a sensor of the vehicle; determining that the receivedtemperature is inconsistent with the weather forecast; andprogrammatically declining the action recommendation if the actionrecommendation was initially accepted, such that the programminginstruction is not sent to the vehicle or is updated so as to cancel theprogramming instruction.

In some embodiments, confidence scores for actions that exceed athreshold is indicative that such action will more likely than not occuragain at a future time. For example, more likely to occur can includesetting some threshold. For example, the threshold can be present to amore than 20%, 30%, 40%, 50%, 60%, 70%, 80%, 90%, 95%, etc., probabilityof occurring. The higher the threshold, the higher the probability ofoccurring—and will reduce recommendations unless they are very certainof occurring. If the threshold is lowered (e.g., user set as apreference or set by factor), the more likely it is that a user will getrecommendations after just a few repeat occurrences. If the threshold ishigh, the system will wait to confirm that this pattern is repeated withcertainty and higher confidence.

In some embodiments, a method can further include: accessing third-partyhistory profiles of other user accounts; examining the actions andmetadata of the third-party history profiles to identify similar actionsand patterns to those of the history profile; adjusting one or more ofthe action recommendations based on the examining, and the adjusting maybe weighted to provide more significance to metadata in the historyprofile than that in the third-party history profiles. Looking tosimilar profiles, the information and recommendations can be providedfrom one or more crowd source systems. In one embodiment, the thirdparty profiles can be from other user of vehicles, say from the samemanufacturer. In one embodiment, data coming from the actual user willbe given more weight than data coming from third parties.

In some embodiments, the action recommendations change over time basedon changes in patterns detected in the history profile.

In some embodiments, changes in action recommendations include removalof previously accepted action recommendations when either override ofactivating the action is detected to occur a number of times or changesin patterns of use of the actions at the vehicle suggested removal ofthe previously accepted action recommendation.

In some embodiments, the third-party history profiles and the historyprofile are defined as one or more databases on storage accessible by aserver that is accessible over the Internet. In one example, the vehicleuses communication logic for communicating with the server over theInternet. In one example, the server further includes logic for sendingthe action recommendations to devices of a user having the user accountfor the vehicle.

In some embodiments, a server executes cloud processing logic to performoperations method operations. In one example, client devices andvehicles devices can communicate with the server and cloud processinglogic to exchange data.

FIG. 16B describes how one of many types of inputs into an assumptionand reasoning logic module 2216 can be compiled over time. Althoughinputs can come from many sources, this particular example focuses oninput into the assumption and reasoning logic module 2216 from past dataoriginating and triggered by user behavior in order for module 2216 tolearn. Past actions 2210 are logged into a database either locally onthe vehicle computer or remotely which are fed into to module 2216. Inthis example, data about when the user's actions are stored, along withunique identifiers that will allow assumptions to be made in the future.

These identifiers include times, dates, rates, capacities, temperatures,frequency, degrees, distance, etc. In this example, the system has beenkeeping track of when the user has been starting his or her engine inthe morning on weekday sand weekends. The system harvests all datapoints associated with given events. These data points 2210 are purelymined data points and no assumptions or reasoning occurs at this point.This data will be used by the assumption and reasoning logic 2216 todetermine future actions.

FIG. 16C describes one example of what an assumption and reasoning logicmodule 2216 may produce using the data points collected on an ongoingbasis in FIG. 16B. Over time, using inputs that are continuallyharvested by a user's action, assumptions are made and refined to aid inmaking decisions for a user in advance or behalf. Module 2216 has takenthe inputs provided by 2210 past data and behavior to determine thatbefore a decision can be made, the user's local or network-storedcalendar should be polled to determine how the user's schedule mightimpact the system's pending actions. For instance, if the system haddetermined that the user typically starts his vehicle at 8 am but theuser's calendar shows a meeting at 730 am located at a location thatdoes not match the current location, the vehicle may assume that the carshould be started at 725. They system will determine its level ofconfidence of the decision and may poll the user for a decision.

The system, by using prior data points has stored assumptions based onconditions, the day it is, the temperature of the environment andhistorical events, that the user will most likely start the vehicle'sengine between 803 am and 805 am, and if the temperature is in the 30sinside the vehicle, the user will most likely set the interiortemperature to between 70 and 80 degrees, it is not likely that the userwill use the are conditioning unit, if there is ice on the windshield,the user will most likely defrost the windshield for 7 minutes beforedeparture, the user usually drives between 15 and 18 miles at this timeof day, the user typically starts the vehicle again in the afternoonbetween 505 pm and 510 pm, if the temperature is in the mid-70 s, theuser usually activates the AC and sets the temperature to 65 degrees,typical weekend behavior, the user typically makes frequents stops, doesnot have a set time the vehicle is started, uses certain APPs at certaintimes and has a history of certain destinations as recorded by GPS.

FIG. 16D describes an example list of decision the decision and actionengine 2218 may take based on information provided by the assumption andreasoning logic module 2216 and sets of assumptions created. Thedecision and action engine 2218 will attempt, using a degree ofconfidence to anticipate what the user will want to do in terms ofengine start and stop, location destinations, preferences oftemperature, driving habits and poll vehicle capacities to ensure theintended path the user usually takes is attainable. For example, theuser usually drives a distance in the morning at a certain time,however, the vehicle's fuel supply will not allow for that distance tobe traveled. Thus, the decision and action engine polls the user as areminder that the user should begin their intended travel sooner thanusual to allow for refueling time.

FIG. 17 illustrates example cloud processing storage system, inaccordance with one embodiment of the present invention. The illustratedexamples show how various user profiles can be managed so that actionstaken by users in their vehicles can be stored, with associatedmetadata. The metadata can include identification of when the action wastaken, can include counters to identify how many times actions weretaken, date parameters for when actions are taken, durations of actions,frequency of actions, time of day, user identification, and othermetrics. For example, inaction can be turning on the heater in thevehicle.

The metadata can identify the frequency of when the heaters turned on,patterns for turning on the heater, settings for the heater, time ofday, time of year, metrics associated with external conditions measuredwhen the heater was activated (weather), etc. As such, when the variousactions are taken by specific users under vehicles, these actions can bemonitored and metadata can be augmented to the specific actions. Thespecific actions can be monitored for various users that may have anaccount with a cloud service provider.

If the user's vehicle is registered with a cloud service provider, thecloud service provider can monitor the actions and identify the metadataor augment the metadata as those actions are taken over time. In oneembodiment, cloud processing can include action analysis logic that cananalyze the frequency, patterns, and other data in the metadata for thevarious actions. Rules can be set for analyzing the metadata, andtriggering or identifying particular actions as relevant.

The particular actions that are relevant can then be further analyzed,or monitored to determine if specific patterns are being satisfied toenable a determination that a particular action has been learned. Asnoted above, a learned actions can be an action that analysis hasdetermined to occur two or more times, or based on a pattern, or whenother conditions confirmed that the action is taking place inconjunction with those other conditions. In one embodiment, when certainactions occur over time or repeat a certain number of times or form apattern, such actions can be assigned a score.

The score can be a confidence score that connotes that that action willlikely occur in the future. If an action is likely to occur in thefuture, it is likely to occur more often than not when certain otherconditions or patterns have dictated that the action will occur in thefuture.

In one embodiment, some actions that are being monitored for specificuser in the users profile or history profile can be assigned variousconfidence scores. The confidence score can be a low confidence score,which is indicative that the action will not always occur or is not morelikely to occur. As a confidence score is increased, it can be said thatthe particular action is more likely to occur than not in the future.

A threshold setting can be set for specific users, or for specificactions. The threshold score can be a setting that dictates when arecommendation for an action should be sent to the user to enable theuser to decide if an action will be programmed into the vehicle. If thethreshold setting is low, it will take fewer repeat actions for therecommendation to be sent. If the threshold score is high, theconfidence level must be very high or higher before a recommendation issent to the user to associate that particular action with a programmablesetting.

In one embodiment, if a recommendation is sent by recommendation engineto the user of the vehicle, that recommendation can either be acceptedor declined. The recommendation can be sent either directly to thevehicle, or to the mobile device of the user register to the vehicle, orto a user account of the vehicle, which is accessible to the registereduser. The recommendations can therefore be sent individually, or can besent in groups. If the user excepts a particular recommendation, thesetting is programmed to be sent to the vehicle. The setting can be senteither upon determining that a recommendation was accepted, or at alater time.

As noted above, the recommendation can be sent individually or in groupsof recommendations. Once the recommendation is accepted and theprogramming sent to the vehicle, the vehicle can communicate back tocloud processing to indicate that the setting has been made at thevehicle. The user settings in the user profile for the vehicle are thenupdated. The user settings include a list of programmed settings for aspecific vehicle. The program settings can either be in response to therecommendations, or in response to active programming by the user whereno recommendation was sent. In one embodiment, the recommendation enginewill also be in communication with the Internet.

The recommendation engine can query the Internet for data in order toreinforce whether or not a recommendation should be sent by therecommendation engine. For example, when the user sets the heater in thevehicle, the recommendation engine will know that the weather around anexterior to the vehicle was at a particular temperature. In this manner,the action analysis can take place to determine if those actions takenat the vehicle coincide with other external factors, such as weather,GPS location, news, social media, calendar data, etc. In one embodiment,the action analysis made by cloud processing can also take into accountactions taken by other 3rd parties, not just the actual user thevehicle. In one embodiment, the 3^(rd) parties can be other users thatare registered with cloud service, or other users that are notregistered with cloud service. In still other embodiments, the 3rdparties can be identified from social networks and an analysis can bemade regarding comments made regarding their vehicles or use othervehicles. In still other embodiments, data can be crowdsourced fromvarious sources.

For example, if similar people take particular actions when thetemperature is at a particular level, then it can be assumed that theactions taken by 3rd parties may also be taken by the user group of theparticular vehicle. In one embodiment, by looking at actions taken by3rd parties, it is possible to make assumptions or collaborativelyfilter certain actions or recommendations. Logic can also be included toidentify rules that should be taken into consideration based onsimilarities found in other user profiles. If the user profiles forparticular demographics show particular actions and associated metadata,then the recommendation engine can take that into account when providingrecommendations to a user. In one embodiment, recommendations made basedon third-party actions and metadata can be weighted.

The weighting can be a factor that reduces the emphasis or confidencelevel or score, as those actions are not taken by the exact individualreceiving the recommendation. For actions taken by the individualreceiving the recommendation, the confidence level or score can beemphasized by providing additional weighting. In other embodiments, thehistory profile of users, which includes the metadata can be analyzedcontinuously by the cloud processing server or servers. In otherembodiments, the history profile and metadata can be analyzedperiodically.

In one embodiment, at a remote location, a user is able to access a userinterface for an application, which provides users access to useraccounts. A user account can be for a user and the user can add one ormore vehicles, objects, data or appliances for remote reporting, viewingand control. In one embodiment, a user is an owner or user of a vehicle.The user can register the vehicle with a remote service.

The remote service can be accessed over the Internet, such as via awebsite or application of a portable device. The remote service canprovide a multitude of cloud services for the user, such as remotecontrol features, remote viewing services, remote alarm controls, remotecamera activation, remote audio/video recording of the vehicle (i.e.,areas around the vehicle and inside the vehicle). In one embodiment, thevehicle is able to connect to the Internet (e.g., when the vehicleengine is off, on, and/or is occupied or un-occupied) to allow a user,via a remote cloud service, to access features of the vehicle. Thevehicle can be accessed when running, when parked, when stopped, whenmoving, etc. The vehicle and its audio recording devices and videocameras can be accessed from remote locations, to allow users toremotely communicate with the vehicle or with people riding or residinginside the vehicle.

The remote communication can also allow a person to communicate remotelywith people standing outside (or inside) of a vehicle. For instance, ifa user is accessing his or her vehicle from a remote location, camerasinstalled in and/or on the vehicle allow the remote user to see a personstanding proximate to the vehicle. The remote user can then communicatewith a person standing proximate to the vehicle using microphones andspeakers of the vehicle.

In some embodiments described herein, vehicles, structures and objectsmay include circuitry and communication logic to enable communicationwith a cloud processing system over the Internet.

In one embodiment, the services provided by the electronic systems of avehicle can include services that access the various components orsubsystems of a vehicle, such as door locks, service histories, userprofiles, audio settings, entertainment settings, mapping functions,communications systems, telecommunication synchronization systems,speakers, heating and cooling functions, auto-engine start/shut-offremotely via smart devices, remote heating/cooling initiation, remoteface-to-face conferencing, etc. The electronic systems within a vehiclecan also provide a user interface, such as a graphical user interface.The graphical user interface can include a plurality of buttons,controls and transceivers to receive input from a user.

The input from a user can also be provided by voice input, facialrecognition, eye-retina scans, fingerprint scans, a combination ofbiometrics, or via a capacitive or regular touchscreen contained ordisplayed within the vehicle, the vehicle's glass, doors, dashboard,etc.

In one embodiment, vehicles can maintain information regarding wherethey are, where they are heading and their destination maintained whichis maintained by GPS and navigation systems on board. The informationcollected and maintained by every vehicle may be mutually exclusive,meaning that only each individual vehicle is aware of its own heading,rate of speed and current location. This information, in one embodimentis crowd sourced and/or crowd shared/consumed for use in for accidentavoidance or other communication. By networking vehicles within acertain radius together, all individually location-aware vehicles becomeaware of all other vehicles in their sphere of influence. Vehicles maynetwork with vehicles in their range using wireless communicationsystems such as but not limited to Wi-Fi, Wi-Gig LTE, cellular, radio,near field communication or other methods.

In one embodiment, the communications of the vehicle and electronics ofthe vehicle will enable direct communication with a user of the vehicle.The user of the vehicle can include, for instance, the owner of thevehicle, a driver of the vehicle, or any third party having access tothe vehicle (either to drive the vehicle, to monitor the vehicleremotely, etc.)

The access to the data can also be encrypted to prevent unauthorizedaccess to the data. GPS and mapping services can also be incommunication with the cloud processing 120 provide data concerning thelocations of the vehicles and activities that occurred to the vehicleswhen at particular locations. The cloud processing 120 can be access bythe vehicles themselves using their electronics and communications, viamobile devices, from home, from work, etc.

In some embodiments, the vehicles may establish peer-to-peer links tofacilitate fast transfer of data. In other embodiments, vehicles maylink to each other using pairing algorithms that allow the vehicles toexchange data using WiFi, Bluetooth, near field communication (NFC), orsome other short range communication protocol.

A user's APP homepage may also include dynamically updating sections inwhich the most important information at a given time may be displayed orsurfaced to a user. If a user has parked in a certain parking area, heor she may want to monitor metrics related to incidents that may haveoccurred to his or her vehicle, vehicles around his or her vehicle, anydynamically received alerts, as well as precaution levels. Additionally,a user may choose to configure his or her APP homepage to display themost pertinent audio and video feeds to their needs.

In one embodiment, the vehicles can communicate directly with each othervia a temporary pairing process. The temporary pairing process can beautomatically enabled when vehicles become too close to each other, forexample. When this happens, local communication between the vehicles,such as a peer-to-peer connection, Wi-Fi connection, NFC connection, orBluetooth connection can be established to enable the vehicles to shareinformation concerning their proximity to one another.

This local communication will enable one or both vehicles to takecorrection actions or alert a driver to change course or triggerautomatic collision prevention measures (e.g., more aggressivenotifications to one or both operators, slow the speed of one or morevehicles, change the driving direction of one or more vehicles, etc.).Once the close proximity communication occurs and some corrective actionis made, the data regarding the occurrence and the actions taken can becommunicated to the cloud system for storage. The information can thenbe viewed by a registered user having access to an account for thevehicle(s).

The various embodiments may be embodied in computer readable media,which is saved in storage. The storage may be saved on cloud storage,data centers, or the like, which are accessible over the Internet. Theaccess may be wired or wireless. In vehicles, the connection to theInternet may be wireless, and the connection can be continuous ornon-continuous depending connection. Code on the vehicle electrons canexecute at least some of the method operations when not connected andother operations are executed jointly between vehicle electronics (e.g.,memory, code and processors of a vehicle) and cloud processing, whichmay implement one or more servers, either virtual or not.

It will be obvious, however, to one skilled in the art, that the presentinvention may be practiced without some or all of these specificdetails. In other instances, well known process operations have not beendescribed in detail in order not to unnecessarily obscure the presentinvention.

The various embodiments defined herein may define individualimplementations or can define implementations that rely on combinationsof one or more of the defined embodiments. Further, embodiments of thepresent invention may be practiced with various computer systemconfigurations including hand-held devices, microprocessor systems,microprocessor-based or programmable consumer electronics,minicomputers, mainframe computers and the like. The invention can alsobe practiced in distributed computing environments where tasks areperformed by remote processing devices that are linked through awire-based or wireless network.

With the above embodiments in mind, it should be understood that theinvention could employ various computer-implemented operations involvingdata stored in computer systems. These operations are those requiringphysical manipulation of physical quantities. Usually, though notnecessarily, these quantities take the form of electrical or magneticsignals capable of being stored, transferred, combined, compared andotherwise manipulated.

Any of the operations described herein that form part of the inventionare useful machine operations. The invention also relates to a device oran apparatus for performing these operations. The apparatus can bespecially constructed for the required purpose, or the apparatus can bea general-purpose computer selectively activated or configured by acomputer program stored in the computer. In particular, variousgeneral-purpose machines can be used with computer programs written inaccordance with the teachings herein, or it may be more convenient toconstruct a more specialized apparatus to perform the requiredoperations.

The invention can also be embodied as computer readable code on acomputer readable medium. The computer readable medium is any datastorage device that can store data, which can thereafter be read by acomputer system. The computer readable medium can also be distributedover a network-coupled computer system so that the computer readablecode is stored and executed in a distributed fashion.

Although the foregoing invention has been described in some detail forpurposes of clarity of understanding, it will be apparent that certainchanges and modifications can be practiced within the scope of theappended claims. Accordingly, the present embodiments are to beconsidered as illustrative and not restrictive, and the invention is notto be limited to the details given herein, but may be modified withinthe scope and equivalents of the description and claims.

What is claimed is:
 1. A computer implemented method processed by aserver that communicates with vehicles and processes informationreceived from vehicles and processes information sent to vehicles,comprising, receiving data from a computing device associated with avehicle, the data being for a user account, the data being received overone or more sessions, the user account having a user profile with aplurality of settings and metadata captured from use of the vehicle;processing, by a learning engine, the metadata captured from use of thevehicle during the one or more sessions of use of the vehicle toidentify learned patterns sensed from the vehicle; and sending arecommendation to the user account associated with the vehicle, therecommendation is based in part on the learned patterns sensed from thevehicle, the recommendation is configured to identify a setting oraction for the vehicle; wherein the setting or action is configured tobe accepted via a user interface associated with the user account toapply said setting on the vehicle or confirm said action for thevehicle.
 2. The computer implemented method of claim 1, whereinprocessing the metadata captured from use of the vehicle is based on amonitoring of systems of the vehicle over time, and the learned patternsare analyzed as satisfying a condition for said recommendation.
 3. Thecomputer implemented method of claim 1, wherein user profile for theuser account includes biometric data, or an image of a face of a person,or a fingerprint of a person, or combinations of two or more thereof. 4.The computer implemented method of claim 3, wherein the image of theface of a person is used at least in part as credential of a user thatis associated with the user account.
 5. The computer implemented methodof claim 1, wherein the metadata captured from the vehicle relate to oneor more of use of APPS, or system components of the vehicle, orenvironment conditions, or historical actions taken by the vehicle, orinput/output controls of the vehicle, or use of buttons of the vehicle,or use of levers of the vehicle, or use of keys or key fobs of thevehicle, or use of a display selections of the vehicle, or use of adisplay interface, or use of a communication action of the vehicle. 6.The computer implemented method of claim 1, wherein the metadatacaptured from use of the vehicle includes captured systems data,captured user input settings, or identification of said user account oranother user account, wherein another user account is for another userprofile to be used with the vehicle.
 7. The computer implemented methodof claim 1, wherein the identified setting by said recommendationrelates to a component or use mode of the vehicle.
 8. The computerimplemented method of claim 1, wherein the identified action by saidrecommendation relates to service of the vehicle or reservation forservice of the vehicle.
 9. The computer implemented method of claim 1,wherein the server is part of a cloud services system, the cloudservices system is provided by one or more of a manufacturer of thevehicle or a third party provider, the cloud services system isconfigured with access to storage for holding said metadata receivedfrom the vehicle and from other vehicles.
 10. The computer implementedmethod of claim 1, wherein the user profile being one of anadministrator profile, a temporary profile, a shared vehicle profile, avalet profile, a child profile, or a custom profile.
 11. The computerimplemented method of claim 10, wherein the shared vehicle profile isfor the vehicle when the vehicle is used via two or more user accountshaving associated user profiles.
 12. The computer implemented method ofclaim 2, wherein said settings or actions relate from one or more of asetting a temperature of the vehicle, a setting a window defrost mode inthe vehicle, a heating a seat or seats of the vehicle, a setting anemergency signal of the vehicle, a setting an emergency signal for help,a setting a restriction or enabling a feature for the vehicle, adisabling the vehicle, a selecting an audio setting, making areservation for service, reporting an error in the vehicle, setting aposition of mirrors of the vehicle, setting to open or crack windowsupon reaching a temperature, setting notifications for recharging abattery if the vehicle is an electric vehicle, setting reminders tocharge upon reaching a predefined battery state if an electric vehicle,setting parameters to identify nearby charge stations if the vehicle isan electric vehicle, setting advertisement settings allowed to bedisplayed via a screen of the electric vehicle, setting maps data,setting communications data, setting navigation data, setting displaysettings data, setting customization of display applications on thescreen of the vehicle, setting suspension parameters for the vehicle,setting auto lock/unlock controls of the vehicle, activating an alarm,setting instructions to receive video feedback from the vehicle upondetection of alarm conditions, setting to call for help when an accidentis detected, setting time of day on vehicle clocks based on local time;setting navigation parameters in the vehicle, setting preferred radiostations, setting sensitivity of collision detection sensors, settingsensor programming, or combinations of two or more thereof.
 13. Themethod of claim 1, wherein the recommendation is one of a plurality ofrecommendations, and said plurality of recommendations are associatedwith a confidence score.
 14. The computer implemented method of claim 1,wherein the metadata is associated with sensor data from the vehicle,the sensor data includes one or more of sensed temperature data,geo-location data, speed data, vehicle condition data, occupantidentification data, number of occupant data, biometric detection dataof an occupant in the vehicle, proximity of surrounding vehicles orobstacles data, voice data, video data, touch data, gesture data,surrounding vehicle shared sensor data, or at combination of two or morethereof.
 15. The computer implemented method of claim 1, whereinlearning engine processes metadata associated with third-party historyprofiles of other user accounts.
 16. The computer implemented method ofclaim 15, further comprising examining actions of one or more of thethird-party history profiles to identify similarity in actions orpatterns to those of a history profile of the user account.
 17. Thecomputer implemented method of claim 1, wherein the learned patternssensed from the vehicle relate to use of settings of the vehicle whilethe vehicle is used via the user account or relate to use of the vehiclecausing sensor data output from system of the vehicle to produce saidmetadata.
 18. The computer implemented method of claim 17, wherein saidserver is one of a plurality of servers associated with a cloud servicessystem that executes said learning engine to process said metadata forsaid vehicle and other user accounts managed for other user accounts andother vehicles, the cloud services system is configured to manage saidrecommendation and other recommendations sent to said vehicle and saidother vehicles.
 19. The computer implemented method of claim 18, whereinthe metadata is associated with sensor data from the vehicle, the sensordata includes one or more of sensed temperature data, geo-location data,speed data, vehicle condition data, occupant identification data, numberof occupant data, biometric detection data of an occupant in thevehicle, proximity of surrounding vehicles or obstacles data, voicedata, video data, touch data, gesture data, surrounding vehicle sharedsensor data, or at combination of two or more thereof.
 20. The computerimplemented method of claim 18, wherein processing the metadata capturedfrom use of the vehicle is based on a monitoring of systems of thevehicle over time, and the learned patterns are analyzed as satisfying acondition for said recommendation.